Re: SVGT 1.2: Appendix C3: SVG Error Processing

> differently in each browser, instead of writing non-conformant marker and 
> getting the same behaviour in all browsers.

But the consequence of this policy is that there is no non-conformant 
markup!  Even compromises likely eplicitly specifying that code be ignored
until a particular recovery point are likely to be treated as "undefined" 
currently is, by browser developers, who will see a competitive advantage
in guessing what the author intended, which leads one to a world were
every construct does something "useful".

Received on Monday, 2 January 2006 13:19:40 UTC