W3C home > Mailing lists > Public > public-html@w3.org > February 2008

Re: Unmatched quotes for attributes (was: Re: Spaces in IRIs)

From: Simon Pieters <simonp@opera.com>
Date: Mon, 04 Feb 2008 00:43:47 +0100
To: "Simon Pieters" <simonp@opera.com>, "Philip Taylor" <pjt47@cam.ac.uk>, "Sam Ruby" <rubys@us.ibm.com>
Cc: "HTML WG" <public-html@w3.org>
Message-ID: <op.t5y2u9e5idj3kv@hp-a0a83fcd39d2.belkin>

On Sun, 03 Feb 2008 23:41:26 +0100, Simon Pieters <simonp@opera.com> wrote:

> This is interesting. A validator would catch this particular case since  
> click, for, full and list" are invalid attributes for <a>, but if you're  
> unlucky the markup happens to match allowed attributes or you're using  
> <embed> where any attribute is allowed.
>
> Some ways to improve this situation:
>
>    * Make lack of whitespace between attributes a parse error. (Not an  
> error in
>      HTML4 but authors generally think it is.)
>
>    * Make " and ' in attribute names a parse error. (An error in HTML4.)

We might want to catch this case too:

    <div class=foo">

...which probably is as simple as banning " and ' in unquoted attribute  
values.


>    * Make the empty attribute syntax conforming only for boolean  
> attributes.
>      (HTML4 allows minimization of enumerated attributes, but authors  
> generally
>      think it's only allowed for boolean attributes. Moreover, IE drops  
> src
>      and href attributes when using the empty attribute syntax.)
>



-- 
Simon Pieters
Opera Software
Received on Sunday, 3 February 2008 23:44:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:12 GMT