[whatwg] Form-associated elements and the parser
ian at hixie.ch
Tue Dec 3 10:39:24 PST 2013
On Thu, 21 Nov 2013, Ryosuke Niwa wrote:
> A start tag whose tag name is "isindex"
> Right now, form element pointer is not null in the following example, so we end up losing isindex element entirely.
> <!DOCTYPE html>
Hm. It's worse than that: <form><template><form> will drop the inner
<form>, because the form element pointer is set.
So, there's several ways we could fix this. We could simply say <template>
isn't valid inside <form> and ignore the whole problem.
Or, we could have a form element pointer stack that parallels the
I guess the latter is best for authors. How do implementors feel about
adding a new stack for the template stuff?
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg