Rimantas Liubertas wrote:
The main thing is, that if parsed correctly by HTML parser XTHML would even "produce" more data, or to say it more exact, browsers would show more. I mean an extra ">" popping up for every <br /> and <img .../>. Those compatibility guidelines rely solely on browsers failing to implement SHORTTAG in correct way.

So standards are created in a "real world" environment, and take
advantage of weaknesses created in the past. Nothing gets broken because
of it - probably because the old rendering is already FUBAR[1] by design.

Now, let us try to prevent that happening in the future, and let the
past take care of its own problems. No need to drag it along or drag it out.

We have more than enough real world problems in need of solutions in
order to get our efforts through in a constantly changing and pretty
buggy set of environments across browser-land. Let us focus on solving
those, and make sure newcomers get it right also - preferably from the
very beginning.


The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help

Reply via email to