- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 2 Jun 2009 09:29:24 -0700
- To: Simon Pieters <simonp@opera.com>
- Cc: Ian Hickson <ian@hixie.ch>, Julian Reschke <julian.reschke@gmx.de>, Kornel <kornel@geekhood.net>, public-html@w3.org
On Tue, Jun 2, 2009 at 4:51 AM, Simon Pieters <simonp@opera.com> wrote: > On Tue, 02 Jun 2009 12:22:56 +0200, Simon Pieters <simonp@opera.com> wrote: > >> Writing HTML documents seems to make this valid: >> >> <a href="©="> >> >> and claims that the attribute value contains just text and no character >> references (since character references end with ";"). >> >> Yet, Parsing HTML documents interprets the above the same as <a >> href="©=">, as far as I can tell. >> >> Now, I guess there are several possible ways to fix this mismatch. >> >> 1. Revert the change. >> 2. Tweak the writing rules so that the ampersand above would be >> ambiguous. >> 3. Tweak the parsing rules so that = is treated the same as 0-9a-zA-Z. > > If action (2) or (3) are taken, then I guess it would make sense to make > "&=" allowed, too. Additionally, I given how easy it is to get unexpected results, I think we should strongly discourage authors from not escaping ampersands. And the best tool that we have for doing that is by making unescaped ampersands non-conformant. / Jonas
Received on Tuesday, 2 June 2009 16:30:29 UTC