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

91–100 of 108 posts

Re: Chrome 22 breaks things

#91

Post by nikcub »

batista wrote: post #13
eckyptang wrote: post #8

Without wishing to piggy back on this thread I feel its a good time to point out that this is exactly why enterprises stick with IE. People are risk averse in businesses.

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

Some of the most advanced CSS and Javascript I have seen for the first time in Enterprise apps. I first saw xmlhttprequest in a Cognos controller, I first saw drag+drop in a browser in another enterprise app.

the Outlook web interface was miles ahead of anything in the consumer space for years.

Re: Chrome 22 breaks things

#92

Post by ivank »

dangrossman wrote: post #37

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…

http://code.google.com/p/chromium/issues/detail?id=146407

Re: Chrome 22 breaks things

#93

Post by buster »

cvalleskey wrote: post #68
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 workin…

I've been using chrome beta for a while (so i'm at 23 now and was at 22 a while) and never saw those problems. How many sites do you know that are broken, apart from your own project?

Re: Chrome 22 breaks things

#94

Post by buster »

eckyptang wrote: post #30
xionon wrote: post #17

Earlier quoted context omitted.

I thought that had more to do with the billions of dollars invested in IE-only web applications and the astronomical cost of upgrading, retraining and supporting thousands of people, not the fear that one version of Chrome will someday break CSS behavior.

No not at all. Most of the LOB applications you see these days work very well in most browsers. Ours works in Firefox, Chrome, IE, Safari perfectly and is entirely plugin free. I've not seen an ActiveX for about 5 years and that was a file upload control. All our fugly desktop integration is done with a broker application which runs on the user's machine and talks to local COM objects via web services. You see an occ…

What is your experience based on?

I've been working with some large enterprises in the past (50k+ employees), all of them only use IE and all of them are full with some crappy ActiveX software, some by HP, some homegrown, it's really full of that crap. :( Even software that would support multi-platform is crippled in a way that only Windows+IE works, because in the projects noone cares if some other browser or (god forbid) another OS is supported.

Re: Chrome 22 breaks things

#95

Post by egeozcan »

zevyoura wrote: post #75
calinet6 wrote: post #64

Earlier quoted context omitted.

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.

Are those problems really specific to enterprise software?

This "Enterprise Software" label doesn't make sense at all, anyway.

Re: Chrome 22 breaks things

#96

Post by egeozcan »

cvalleskey wrote: post #9
nthitz wrote: 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.

I agree. Add too much salt to the food and people will say that you've ruined it. Some people won't notice it because they are less sensitive or for other reasons but the food, for some, is ruined.

This happens a lot with the software development where one simple bug in your application makes the user say that "it doesn't work". We, as developers, tend to get mad when all our work is deemed unfunctional because of a simple error but we usually don't see that it is a "simple error" only from our perspective.

Re: Chrome 22 breaks things

#97

Post by tylermenezes »

Interesting bug that I was just running up against which might be related. I was trying to draw some text in a small box, but, while it worked in all other browsers, Chrome 22 was adding what appeared to be extra line height for no reason. The code looked roughly like:

    TEST
    
    div > span {
        line-height: 0;
        margin: 0;
        padding: 0;
        font-size: 12px;
        display: block;
        height: 12px;
    }
Yet the text was being drawn dramatically outside of the box!

Turns out that this only happens in Chrome 22 when it's inside a list with list-style-type: disc.

Re: Chrome 22 breaks things

#100

Post by bzbarsky »

cramforce wrote: post #89
bzbarsky wrote: post #83

Earlier quoted context omitted.

Really? Can you point to the spec change? Did I miss a working group decision on this somewhere? Last I checked, the discussion on this got nowhere, with WebKit folks claiming this change was needed to optimize stuff and Opera and Mozilla folks claiming that optimizing scrolling worked just fine without this behavior change...

http://www.w3.org/TR/CSS21/zindex.html

This has no such change. Try again.
Post reply on HN