Live data from Hacker News

Chrome 22 breaks things

chrisvalleskey.com

41–50 of 108 posts

Re: Chrome 22 breaks things

#42

I've been seeing color abberations in text since my PC updated to Chrome 22. Most noticeable has been blue links showing up with a purple tint -- significantly different from the color showing in the Inspector. It's browser-wide, with extensions disabled -- I first noticed the change in link color on a Reddit comment thread, then saw it on Google Plus and my own website as well. http://i.imgur.com/Wjay2.png Has anyon…

Smells like subpixel aliasing?

Re: Chrome 22 breaks things

#47

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 t…

What does the spec say? is there a bug opened already? or are all the browsers wrong and Chrome is right?

Re: Chrome 22 breaks things

#48

I've been seeing color abberations in text since my PC updated to Chrome 22. Most noticeable has been blue links showing up with a purple tint -- significantly different from the color showing in the Inspector. It's browser-wide, with extensions disabled -- I first noticed the change in link color on a Reddit comment thread, then saw it on Google Plus and my own website as well. http://i.imgur.com/Wjay2.png Has anyon…

I've noticed this as well, for blue links. It's really bugging me. Are you aware of a workaround?

Edit: I'm on a Mac, 10.7.5, FWIW

Re: Chrome 22 breaks things

#50

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 t…

How much content does this break? Was this discussed on one of the public mailing lists? If so, does anyone have a link to some relevant discussion? (I would love to hear the various positions regarding breaking existing content to bring an optimization used by browsers people generally consider to render things weirdly to all browsers.)
Post reply on HN