2007/1/1, Geoffrey Sneddon:
On 1 Jan 2007, at 16:59, Asbjørn Ulsberg wrote:
> the <base> element has no place in an HTML fragment, so its meaning
> is (although most browsers wrongfully supports its presence
> anywhere in an HTML document) unspecified.
Web Applications 1.0 (keeping with the real world) defines that it
should be moved to HEAD within the DOM tree.
I suppose HTML within Atom is rather processed as "innerHTML", so
there is no "head pointer", and the <base> element is just appended as
a child of the current node (along with a "parse error" !)
Why, may I ask, MUST (under the RFC 2119 definition) HTML content be
a fragment ("HTML markup within SHOULD be such that it could validly
appear directly within an HTML <DIV> element, after unescaping." -
note the word SHOULD, not MUST, implying that you can have a full
HTML document within)?
Yes, you could, in the sense that the Atom document wouldn't be
"invalid", but you shouldn't expect it to be processed as a "full HTML
document".
The "SHOULD" implies that Atom processors are OK if they process HTML
"content" as "innerHTML" on a <div> element.
--
Thomas Broyer
