Live data from Hacker News

Chrome 22 breaks things

chrisvalleskey.com

1–10 of 108 posts

Re: Chrome 22 breaks things

#3
Chris, the position: fixed z-index issue is more widespread than you have there; I'm trying to come up with a case for reliable repro, but I just bumped into it a bit ago and had to redo some things to work around it. (full disclosure, I'm one of Chris's coworkers)

Re: Chrome 22 breaks things

#5
for position: fixed and changed stacking contexts, you're likely running into this:

http://updates.html5rocks.com/2012/09/Stacking-Changes-Comin...

Basically, the position: fixed on the parent of the span you're trying to put on top is now making the parent its own stacking context, which means that all children will be stacked relative to each other, not to the first absolutely or relatively positioned ancestor of the parent, as it was before.

The easiest fix is to set the z-index on the parent, since that will correctly stack it relative to its sibling (your other position: fixed element). The other way is to give the sibling that you want to be below the other content a negative z-index, since that will, again, specify it in the stacking context you want to affect. Both of these fixes should render correctly in older browsers (I believe).

This is annoying when it affects existing content, but it is part of the spec now (and it's apparently how mobile browsers have always rendered it).

Re: Chrome 22 breaks things

#7
I don't know if this is related, but I had an issue with flash yesterday which seems to correspond to the Chrome 22 release.

I was playing a game which had never had a serious issue before, and I noticed that the timing of things was way, way off. At first, I thought that my system was just lagging - I had a server VM running, Firefox (my main) always has a ridiculous number of tabs open, and I was playing the game in Chrome because I don't like logging into Facebook from my 'everyday' browser - but shutting down the most resource intensive applications did nothing for the game.

Eventually I checked the plugins page and noticed that Chrome's built-in Flash plugin had re-enabled itself - I disabled it a couple weeks ago due to some video streaming issues - and it was once again the default plugin for those applications, therefore overriding the (higher version) system wide install.

I'm really hoping I'm not going to have to babysit Flash every few weeks when Chrome updates, especially since there isn't always a visual cue that you're running a new version of Chrome.

Re: Chrome 22 breaks things

#9
post #6

Talk about an alarmist title of "breaks everything...". Appreciate the HN Mod changing it.

Oh, that's what happened? Apologies for the alarmist title, but depending on your site's CSS this can completely destroy its usability. I meant it in the sense of a user saying everything on a site is broken, not that everything in Chrome 22 is literally broken.

Re: Chrome 22 breaks things

#10

Additionally, Chrome 22 changed the behavior of -webkit-font-smoothing: antialiased so that the weight of fonts looks much different than it used to when this was enabled. It makes icon fonts look especially bad. http://code.google.com/p/chromium/issues/detail?id=152304

I was going to say the same thing. I'm glad I'm not the only one who was bothered by this.
Post reply on HN