Quoting Ian Hickson [EMAIL PROTECTED]:
The first draft of the HTML5 Parsing spec is ready.
Great!
It's not 100% complete. Some of the things that need work are:
Interaction with document.open/write/close is undefined
How to determine the character encoding
Integration with quirks
Christian Schmidt wrote:
Quote from the current working draft (10 January 2006)
http://whatwg.org/specs/web-forms/current-work/#the-change:
UAs may delay firing the input event if the data entry is rapid.
Authors must not rely on this event firing once for each key press,
mouse input, or
Ian Hickson wrote:
So...
The first draft of the HTML5 Parsing spec is ready.
[...]
In section 8.2.1. Tokenisation, should the sentence Command and
character tokens have data read Comment and character tokens have
data?
On 2/3/06, Gervase Markham [EMAIL PROTECTED] wrote:
Shadow2531 wrote:
O.K. Then, it should be getElementByClassName*s*() where you have
have 1 or more classname arguments. If you pass more than 1 class
name, both class names have to be present in the classname attribute
for the element
On Mon, 13 Feb 2006, Dan Brickley wrote:
Any plans for a test suite? eg. pairs of input files and normalised
output? (if that makes sense...).
I'd strongly recommend people put off creating a test suite until the spec
is in more than a first draft, but yes, on the long term this is
On Tue, 14 Feb 2006, Alexey Feldgendler wrote:
It's not 100% complete. Some of the things that need work are:
Interaction with the load event is undefined
What's that for? I think it shouldn't be defined in the parsing spec.
Well, it's not strictly part of the parser section I
On Tue, 14 Feb 2006, Anne van Kesteren wrote:
However, none of the above are particularly critical to the parsing.
Attribute parsing is. And there are some special cases made for that
here and there. It would be good if that was specified as well.
Oh, crap, forgot about those. I even
