Chrome doesn’t take no for an answer

And the series continues…

This time it’s Chrome. Chrome is an excellent browser, but some dialogs are weird… And some are not taking no for an answer.

The dialog below asks us whether we want to recover tabs that were opened before the browser crashed. Curiously there is only one button for us to answer…

chrome-doesnt-take-no-for-an-answer

Continue reading

The Breaking Float Bug is back!

Back in september of 2010 I wrote a blog post about the Breaking Float rendering bug I found in WebKit, the rendering engine backing the Safari, Chrome and Opera browsers. In april of 2013 the WebKit team landed a patch which would eventually end up in the browsers relying on WebKit. Case closed right? Well, not quitte…

Blink brought it back

blinklogo

Coincidentally, in the same month that the Breaking Float bug was fixed, Google forked WebKit into a new project called ‘Blink’. And the fix to the Breaking Float bug was not in the fork. Over time, the Chrome browser switched over to using Blink instead of WebKit, bringing back the issue in all it’s breaking glory.

Continue reading