MikeGale wrote:I have the impression that significant pieces of the web are becoming unusabale to some browsers. I think there's a wave of web developers who only develop for their preferred browser AND have convinced big companies to use their talents.
Yeah sorry I was attempting to make the rant as short as possible.EDIT: The post to which I'm replying seems to have changed a bit, since I originally posted this. It originally said that I had HTML5 backward.
I test in all those browsers and regularly build Chromium from git. Some examples? Do you have any idea what specifically about these websites tends to be the blame? Like I said, as of late, all browsers are using literally the very same HTML parsing, even mostly share the same implementation, so there's no chance at least on the markup side of things that the interpretation of even old broken code could result in building a different DOM on most current browsers. If markup is to blame then it should always be consistently broken in the same way.I increasingly find sites that simply don't work in one of the browsers. This is not some trivial eye candy effect, it's so bad that I need to fire up another browser and paste in the URI to get anything usable.
ormaaj wrote:Hell, CSE gives me extra errors the more "correct" i'm being as there's no way it could understand why things are being done a certain way against it's overgeneralized generic advice that mostly isn't applicable. That isn't necessarily a bad thing. I can see the value in helping guide beginners except perhaps giving an overly simplified view of the nuances of various behaviors.
ormaaj wrote:I would Imagine CSE throws a hissy fit when it sees code like this: http://www.google.com/404
Google 404 page is the way it is for a reason and not incorrect (though whether or not good practice may be a bit controversial).
I test in all those browsers and regularly build Chromium from git. Some examples?
It's quite the trendy marketing gimmick indeed.
I don't think any automated tool could give meaningful numbers
Albert Wiersch wrote:On that note, if there is anything specific you want improved in CSE HTML Validator, then please post it to another topic in the appropriate CSE HTML Validator forum with as much detail as you can provide and I would be happy to see if the output or checking could be improved.
Yes, CSE HTML Validator tries to enforce better structure, though I'm thinking I may have CSE HTML Validator try to assume the missing tags (head, body, etc) with an optional warning message in the next major release. Not sure on that yet, just a thought.
Users browsing this forum: No registered users and 1 guest