Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome 22 breaks things

chrisvalleskey.com

Post reply on HN
Print view View original

61–70 of 108 posts

Re: Chrome 22 breaks things

#61

Post by AgentConundrum »

paulhodge wrote: post #51
AgentConundrum wrote: post #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 i…

I've also starting having some awful performance hitches involving Flash, which might be related. Sometimes if I watch a Youtube video, the whole browser window (not just the current tab) locks up for a few seconds. Just started happening a few days ago, on Chrome for Mac.

As I said in my last comment, Chrome has its own built-in Flash Player. Even if you have another player installed on your machine, the built-in one overrides it unless you specifically disable it.

If you have another Flash player installed, go to chrome://plugins and disable the one that was installed with Chrome. It's obvious by the 'Location' which one this is, at least on Windows. I don't have a Mac so I can't help you there.

It's possible that this is just a problem with Flash 11.3. When I was having the video issues a few weeks ago, I installed the newer 11.4 version. Chrome's built-in player still calls itself 11.3. I don't know if it's that Flash Player version that's having the issue, or Chrome's built-in version specifically. My only specific complaint was that Chrome 22 re-enabled the built-in player without my consent.

Re: Chrome 22 breaks things

#62

Post by tanepiper »

Every issue I've had recently with something breaking has been with Chrome - we see new issues cropping up almost weekly.

As much as I hate developing for IE, I know the issues at hand and know the solution to fix it will be stable - with Chrome, not so much.

Re: Chrome 22 breaks things

#63

Post by jamesr_chromium »

saurik wrote: post #50
magicalist wrote: post #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 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.)

This was proposed here on the CSS WG public mailing list: http://lists.w3.org/Archives/Public/www-style/2012May/0473.h...

Re: Chrome 22 breaks things

#64

Post by calinet6 »

eckyptang wrote: post #22
batista wrote: post #13

Earlier quoted context omitted.

Enterprise apps using IE have 1/100 of the design complexity of sites that are affected by these changes.

You'd be surprised. The amount of CSS/HTML that goes into your typical LOB application is quite large and the applications are typically orders of magnitude more complicated than "sites" as you mention. The piece of kit I work with has approximately 900 ASP.Net MVC views... I just ran CLOC. We have 6.2 million lines of code in 14 different languages!

It's orders of magnitude more complicated, and generally for no good reason. There are often conflicting CSS rules, or 100 lines of cruft when 10 lines might work just fine.

And yes, things break all the time, often for unknown or unexpected reasons, and it's sometimes close to impossible to figure out why and fix the bug.

The enterprise software world is scary.

Re: Chrome 22 breaks things

#65

Post by jamesr_chromium »

mmccaff wrote: post #27

I ran into the z-index issue yesterday with an internal application that uses Twitter Bootstrap. It had been working perfectly for months, and then became unusable. After the new Chrome was pushed out, Bootstrap's modal dialogs were hidden behind the backdrop and therefore inaccessible. It might have been an edge case related to the layout of this application, but ultimately I ended up having to patch bootstrap.js to…

If I understand correctly it's the latter. Make sure the z-index is set on the position:fixed element, not elements inside of it. See http://updates.html5rocks.com/2012/09/Stacking-Changes-Comin...

Re: Chrome 22 breaks things

#66

Post by jamesr_chromium »

cvalleskey wrote: post #45

While my server deals with the traffic, here are the important bits: - Floats don’t push block content down ( http://jsfiddle.net/cvalleskey/WD9pB/ ) - Z-index breaking when element is a child of a fixed parent ( http://jsfiddle.net/cvalleskey/9S3S8/ )

For the second issue, please read http://updates.html5rocks.com/2012/09/Stacking-Changes-Comin...

Re: Chrome 22 breaks things

#67

Post by jamesr_chromium »

AlexMax wrote: post #49

Something else I personally noticed with Chrome 22 is that Doxygen's menu bar now appears to be totally wonky. http://i.imgur.com/zHSYQ.png It happens with every 'last' menu item. No idea where that came from, but it's the first time I've noticed a Chrome upgrade in a long while.

Could you please file a bug at http://new.crbug.com/ with a link to an example doxygen-generated page showing the issue? This doesn't look like something I'm familiar with.

Re: Chrome 22 breaks things

#68

Post by cvalleskey »

jere wrote: post #41

>Chrome 22 Breaks Everything Followed by two things that are broken.

As I said earlier, I didn't mean that Chrome is completely, literally broken. I meant in the sense of a user having just updated their version of Chrome, going to a site, and not being able to do anything. For me and a few coworkers, this was exactly what happened to us when we started noticing these two issues last night. These two relatively minor CSS bugs have broken the functionality of a site we have been working on to the point where it is unusable.
Post reply on HN