- From: Shelley Powers <shelleyp@burningbird.net>
- Date: Tue, 09 Jun 2009 12:39:59 -0500
- To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- CC: "public-html@w3.org WG" <public-html@w3.org>
Lachlan Hunt wrote: > Shelley Powers wrote: >> Lachlan, you misread my statement. I was referring to elements that have >> been made obsolete in the HTML5, or that have never existed. The >> "non-conforming" elements. It was a general statement. > > I was responding to this statement of yours, which seemed to indicate > that you thought the font element must not be supported. Sorry if > I've misunderstood. > > "According to the HTML 5 spec, FONT could then be non-conformant, > which means, if I read the HTML 5 spec correctly, user agents _must > not_ support the element." > My statement was based on the fact that FONT was deprecated in HTML 4.01, which means it could be safely obsoleted in HTML5. The more important point was that according to my understanding of the spec, non-conforming elements _must not_ be supported by user agents, which is behavior differing from the previous HTML spec. >> As for font element, I see the section on rendering, but I can't find >> the parsing section. Do you have a direct link? I looked to see if it >> was still deprecated, but just can't find anything about this. > > Search this section for occurrences of "font". This is the multipage > version, so it shouldn't crash your browser like the single page. > > http://www.whatwg.org/specs/web-apps/current-work/multipage/syntax.html#parsing-main-inbody > > > Or, here's the single page W3C version. > > http://dev.w3.org/html5/spec/#parsing-main-inbody > OK, thanks, I found something with that page. Just general parsing rules, nothing about the current state of the element. Again, though, I don't think this was the key bit of discussion that Sam was hoping to have with his question, but I appreciate you pointing out where to find font in the HTML5 spec. Shelley
Received on Tuesday, 9 June 2009 17:40:39 UTC