Implied Context Parsing (DocumentFragment.innerHTML, or similar) proposal details to be sorted out

Ok,

So from the previous threads, there are appear to be three issues to
resolve, and I'll list the options that I've noted.

I'll follow up with my perspective of pros/cons and ask others to do
the same. Please point out options or issues that I've missed.

--------
Issue 1: How to handle tokens which precede the first start tag

Options:
a) Queue them, and then later run them through tree construction once
the implied context element has been picked

b) Create a new insertion like "waiting for context element", which
probably ignores end tags and doctype and inserts character tokens and
comments. Once the implied context element is picked, reset the
insertion mode appropriately, and procede normally.


-------
Issue 2: How to infer a non-HTML implied context element

Options:
a) By tagName alone. When multiple namespaces match, prefer HTML, and
then either SVG or MathML (possibly on a per-tagName basis)

b) Also inspect attributes for tagNames which may be in multiple namespaces

c) Allow for inline name spacing of elements which would normally
inherit the proper namespace from <svg> or <math>

d) Somewhat orthogonal, but later allow for <template> to have an
optional context attribute (e.g. <template context="svg">), which
explicitly picks a context element.

e) Some combination of the above.

-------
Issue 3: What form does the API take

a) Document.innerHTML

b) document.parse()

c) document.createDocumentFragment()

Received on Friday, 11 May 2012 19:04:36 UTC