tyes funky html error catcher, nesting enforcement thingee doesnt handle </br> in a way that I think it should. IMO such tags that arent matched by an opening br tag should be silently "fixed" and not marked as an error.
As for "silently": User settings, "HTML error reporting level". The default is to silently fix everything with the user having several levels of optional error reporting.
It was quite a while before I 'got' part of what you meant here. You want </br> to be changed to <br /> if there is no opening <br>? Do you want to do this only for empty tags like BR and HR?
I'm not sure that is a good idea in either case. <br> already becomes <br /> and isn't tracked as far as nesting since it doesn't nest. I don't think I want <br></br> to become <br /><br />, but then I'm not sure how common these types of usage are. If some popular browsers already treat </br> as <br />, then that is likely an indication (and perhaps a cause) of how common that particular mistake is.
And I don't think it's the right idea for tags that nest either.
When HTML nesting enforcement becomes manditory, then everyone will be shown such errors when they preview and they can fix such ambiguous errors which will always be ignored as far as formatting goes.
- tye
In reply to Re^7: Total speculation? (HTML fixing)
by tye
in thread Total speculation?
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |