Re: Is IE8 already a legacy browser? Google thinks so.
by Silhouette on Sunday May 22, 2011 @07:36AM
(#2573093)
> You already said your clients aren't asking for it and you're not providing it, are Chrome and FF honestly breaking your HTML4 and CSS2, or are you just exaggerating the problem rolling releases cause?
Yes. See the examples in my earlier posts to this discussion, several of which have directly broken my (and many other people's) sites for customers using those browsers.
> Because given the choice between slow as shit browser releases tied to OS updates and anything else, I'll choose the latter because it's less headache.
False dichotomy.
Re: Is IE8 already a legacy browser? Google thinks so.
by yuhong on Saturday May 21, 2011 @11:57PM
(#2572565)
>are Chrome and FF honestly breaking your HTML4 and CSS2
I think he is not saying that they are breaking the sites right now, just that occasionally bugs happen in chrome that can break the sites.
You already said your clients aren't asking for it and you're not providing it, are Chrome and FF honestly breaking your HTML4 and CSS2, or are you just exaggerating the problem rolling releases cause? Because given the choice between slow as shit browser releases tied to OS updates and anything else, I'll choose the latter because it's less headache.