4 ms·
> What would be weirder, seeing the page either render fully or blow up, or seeing a page start rendering and then at some point be replaced by an error message
by bct 15y ago
> What would be weirder, seeing the page either render fully or blow up, or seeing a page start rendering and then at some point be replaced by an error message?
Who says the page has to be replaced? Webkit and Opera (IIRC) happily render the page up to the first error that they encounter.
Gecko's decision to do the YSOD was a bad one.
- masklinn 15y ago> Who says the page has to be replaced? Webkit and Opera (IIRC) happily render the page up to the first error that they encounter. That shocks me quite a bit. This definitely didn't use to be the case for Safari, early versions implemented draconian XML error handling and refused to display non-well-formed documents. > Gecko's decision to do the YSOD was a bad one. Meh.
- bct 15y agoIt's still draconian error handling, all the spec says is that you have to stop parsing and notify the user. > Meh. There were many circumstances that prevented the adoption of XHTML-as-XHTML. One of them was the fact that your users would get a cryptic error page, with no context, if something went wrong. What Webkit does is much less threatening.