3 ms·
I'm sorry you're getting downvoted for that little insight. I won't give any contractual undertaking to a client that anything I produce will run on Chrome whe
by Silhouette 16y ago
I'm sorry you're getting downvoted for that little insight.
I won't give any contractual undertaking to a client that anything I produce will run on Chrome when delivered, because it's a moving target and for some projects it updates faster than a complete test cycle.
If Mozilla are now switching to crazy-fast auto-updates as well, then I'm going to have to start excluding Firefox too.
At this rate, IE will be the only browser I will be able to commit to testing on and supporting. If that's not irony...
- evilduck 16y agoOh great, someone to usher in a whole new generation of "This site only supported in Internet Explorer" javascript popups. 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.
- yuhong 16y ago>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.
- Silhouette 16y ago> 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.