On Wed, 4 Dec 2013, Ryosuke Niwa wrote: > > Now that I've implemented the new behavior in WebKit, I'm not certain > completely ignoring the form element pointer is the right behavior here. > > That would mean that we'll allow nested form elements and isindex > element will create its own form element even if it's inside another > form element inside template element. > > Is that behavior really desirable?
Why would it not be? I think the only reason it's not desireable outside of <template> is back-compat. If there's something I'm missing, though, let me know! (Note that we're only talking of non-conforming content here anyway.) -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'