[whatwg] Form-associated elements and the parser
ian at hixie.ch
Wed Dec 4 11:01:40 PST 2013
On Tue, 3 Dec 2013, Ryosuke Niwa wrote:
> On Dec 3, 2013, at 3:51 PM, Ian Hickson <ian at hixie.ch> wrote:
> > On Tue, 3 Dec 2013, Ryosuke Niwa wrote:
> >> On Dec 3, 2013, at 10:42 AM, Adam Barth <abarth at eecs.berkeley.edu>
> >> wrote:
> >> Do we really need a stack? Can't we set the form element pointer
> >> aside when we push the first template element and restore it when we
> >> pop the last template element?
> > We could; in fact that might be sufficient because when the template
> > is cloned, all the special associations are lost anyway, IIRC. So the
> > form element pointer would be useless anyway in the template on the
> > long run.
> Right. I also think that not associating form elements with forms
> inside/outside template elements might be more natural to authors given
> their inert nature.
Well, they're still associated with forms inside (e.g. if they are
children or have a form="" attribute).
I've changed the parser spec to ignore the form element pointer for
<isindex> and <form> inside <template>.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg