On Tue, Sep 9, 2008 at 8:30 AM, Jay R. Ashworth jra@baylink.com wrote:
On Mon, Sep 08, 2008 at 03:35:10PM -0700, Brion Vibber wrote:
Even if browsers support it I would expect to see a lot of bots and spiders choke on it -- it's bad enough a lot don't understand that "&" in an <a href="..."> needs to be decoded as "&"... :)
Something I have always thought was breakage in the spec. *It's inside quotes*, people; it is outside your domain.
Not a tenable argument, because HTML entities are needed as much inside quotes as anywhere. " or ' is needed to escape those characters. Moreover, in a non-Unicode character set, you'll typically need to use entities to get most Unicode characters. As soon as entities are needed, you need & to specify a literal ampersand. It would be impossible to say that & doesn't decode to & in quotes -- you wouldn't be able to specify a literal string like """.