veyepar: Tales from the Trenches: Battling Browser Bugs for "Fun" and (Non-)Profit

Author(s):	Roan Kattouw
Location	Case Room 2
Date	jan Thu 15	Days Raw Files
Start	10:40	First Raw Start	10:20
Duration	0:45:00	Offset	0:19:31
End	11:25	Last Raw End	11:33
Chapters	00:00
Total cuts_time	42 min.

http://lca2015.linux.org.au/schedule/30097/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Tales_from_the_Trenches_Battling_Browser_Bugs_for_Fun_and_NonProfit.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Web development used to be HARD. You basically had to rewrite your code for every new browser you wanted to support. But with modern browsers and libraries like jQuery, those dark days are over. Or are they? We pushed the limits of what the web can do while building VisualEditor (the new editor for Wikipedia) and found plenty of hilarious, insane, amazing and horrifying bugs in browsers, even in 2014, even without pushing the limits very hard. All we needed to do was go just a bit off the beaten path. If you're just trying to put a UI around a server-side application, the web is pretty seamless these days, but if you're trying to build an application that runs on the client, you'll find that doing interesting things in browsers is hard, even things you'd expect to be easy.

In this talk I'll share some examples of browser bugs that made us laugh (what happens if you close a tab while it's reloading?), some that made us cry (what if your <img> tag has no src but has an alt text?), and some where we found creative workarounds (how do you convince the browser to make box-shadows behave correctly?). I'll also talk about things that should be really simple and how hard it was to get browsers to do them right.

Comment:

production notes