71–80 of 108 posts
I've also noticed issues with animations in Chrome 22. Everything is prefixed properly and works well in other Webkit browsers like Safari. Chrome doesn't even run the animation, it just flashes and shows up. Anybody else have this issue?
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…
Maybe it's just me, but I swear I didn't do anything weird to my system...
Earlier quoted context omitted.
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.
Oh, and the entire site didn't work in IE6, it was developed / tested entirely targeting Firefox, despite the IE6 requirement being in the spec (and it ONLY needing to work with IE6).
Earlier quoted context omitted.
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.
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
Well it is experimental for a reason. As quoted from the bug report > The webkit-font-smoothing css property is, contrary to the summary, still working. It is still respected, as no lcd font smoothing is being applied. However, the bug where it also affected the weight of the text as a side effect has been fixed. Though it's worth noting they are looking into whether the purpose (and thus the function) of this partic…
Designers and typographers are pissed. Even if it's "right" as the chromium devs seem to insist, it doesn't change the fact that fonts look like shit, and don't look like type designers intended them to render.
http://code.google.com/p/chromium/issues/detail?id=152386 `display: -webkit-flex` disables `overflow: hidden`
Flexbox in general is still experimental; only Chrome 21+ supports the new spec.
http://store.apple.com/br/configure/MC976BZ/A?
Whereas renders normally in Firefox and Chrome 21...
Talk about an alarmist title of "breaks everything...". Appreciate the HN Mod changing it.
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/ )