Re: Where is processing of binary attributes covered?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Philip Taylor writes:

> In particular, the tokenizer state machine will result in a start tag
> token with name "input" and with one attribute, which has name
> "disabled" and value "banana". That feeds into the tree construction
> algorithm, which will http://whatwg.org/html5#insert-an-html-element
> which will http://whatwg.org/html5#create-an-element-for-the-token
> which requires "the attributes on the node being those given in the
> given token". No error recovery occurs while parsing this case. The
> attributes in the DOM are (very nearly) always exactly what was in the
> input document.
>
> The only kind of error recovery in this case is that
> http://whatwg.org/html5#concept-fe-disabled defines the element to be
> disabled if the 'disabled' attribute exists on the element in the DOM,
> regardless of the attribute's value.

Hmm.  OK, I misunderstood.  I thought that in general the DOM which
resulted from parsing was 'conformant', i.e., would if serialized by a
conformant document, but it appears I was mistaken.

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFKuomokjnJixAXWBoRApniAJ4lCVIjJ2j+F7hwlIteaVNiuIZNxQCfbYeA
p12WtG+aLX8+13zLnewYBv0=
=awfk
-----END PGP SIGNATURE-----

Received on Wednesday, 23 September 2009 20:49:19 UTC