4 ms·
> they ignore your typos and unsupported features gracefully I wish there was a browser version that would handle these errors loudly rather than silently. The
by afarrell 9y ago
> they ignore your typos and unsupported features gracefully
I wish there was a browser version that would handle these errors loudly rather than silently. The fact that React does some of this is rather nice.
- pjmlp 9y agoThat was one of the goals of XHTML....
- yoz-y 9y agoI find it quite baffling that we have gone to such lengths to make html/css resilient. I know of no other language/format that does this. Can you, for example, make a half broken PDF and would it still render?
- apatters 9y agoThe ones doing the implementing are the browser vendors and it's a competitive disadvantage for them to not render every site on the web as best as they can. Consumers who come across a broken site will blame the browser and switch to a different one.
- yoz-y 9y agoHaven't thought of that. It does make sense, the incentives are all wrong thinking about it. Publishers want the sites to be made quickly, browser vendors need market share and users have no patience and very low bar for acceptance.
- thristian 9y agoAt a previous job, a colleague was working on PDF parsing and rendering; he told me that Acrobat Reader will successfully load and display terrifyingly broken PDFs, and it's far more resilient than any of the open-source PDF-rendering tools. So yeah, I bet you can.
- my_ghola 9y agoPhp gets away with making many things warnings instead of errors. So it seems to have been made with the same mentality as html and css.
- paulddraper 9y agoYes. Adobe in particular will accept a ton of crap
- blattimwind 9y agoBrowsers log CSS and JS errors. There was an Old-Firefox extension giving you error counts in the menu bar.