2 ms·
> HTML5 parsing is completely specified and definitely compatible, even the error cases. Counter argument: then why do conditional comments behave differently
by cookiengineer 6y ago
> HTML5 parsing is completely specified and definitely compatible, even the error cases.
Counter argument: then why do conditional comments behave differently in each browser engine?
I am not talking about trident, but about CSS hacks for presto, gecko, webkit and blink as well.
If every browser would render as specified, we wouldn't have that outcome.
As developers test on webkit/blink primarily, chances are very likely things will not behave the same in other engines, and if blink violates the spec then everybody will also have to violate the spec.
The internet is built on such bad standards that you cannot even rely on HTTP to work correctly. 206 partial content headers behave differently among all web servers and proxies, and even nginx violates the spec there when it comes to multiple ranges, let alone chunked transfer encoding support.
- dragonwriter 6y ago> > HTML5 parsing is completely specified and definitely compatible, even the error cases. > Counter argument: then why do conditional comments behave differently in each browser engine? They don't. IE5-9 sees conditional comments specially, others don't. > I am not talking about trident, but about CSS hacks for presto, gecko, webkit and blink as well. CSS isn't HTML5, and those hacks aren't conditional comments, and don't rely on parsing differences. > If every browser would render as specified The claim was about parsing HTML5 and generating a DOM, not rendering.