>IOW, if you design a browser to accomodate a 20% error rate, >designers will allow pages to pass with 25% bad code. If you >change to 25%, the designers will allow 30%. It's a negative >feedback loop. I can't think of any reason why not closing 100 tags would be of benefit to anyone (well, aside from bandwidth trolls!). Of course an author should fix that. But as a browser I don't believe it should have any limit to the types of errors it should attempt to overcome in order to finally render a page - certainly not something as trivial as a fixed number of unclosed tags. For me, personally, I wouldn't recommend any software that can't cope with broken input - that's a flaw, not a political statement.
- Re: Mozilla's rendering of slightly buggy HTML Jason Bassford
- Re: Mozilla's rendering of slightly buggy HTML Henri Sivonen
- Re: Mozilla's rendering of slightly buggy HTML Dave Huang
- Re: Mozilla's rendering of slightly buggy HTML David Gerard
- Re: Mozilla's rendering of slightly buggy HTML Matthew Cruickshank
- Re: Mozilla's rendering of slightly buggy HTML Christopher Jahn
- Re: Mozilla's rendering of slightly buggy HTML Christopher Jahn
- Re: Mozilla's rendering of slightly buggy HTML Dave Huang
- Re: Mozilla's rendering of slightly buggy HTML Christopher Jahn
- Re: Mozilla's rendering of slightly buggy HTML Matthew Cruickshank
- Re: Mozilla's rendering of slightly buggy HTML Jason Bassford
- Re: Mozilla's rendering of slightly buggy HTML David Gerard
- Re: Mozilla's rendering of slightly buggy HTML Chuck Simmons
- Re: Mozilla's rendering of slightly buggy HTML Matthew Cruickshank
- Re: Mozilla's rendering of slightly buggy HTML Scott I. Remick
- Re: Mozilla's rendering of slightly buggy HTML Scott I. Remick
- Re: Mozilla's rendering of slightly buggy HTML Matthew Cruickshank
