[whatwg] Form-associated elements and the parser
rniwa at apple.com
Thu Dec 5 08:36:54 PST 2013
On Dec 5, 2013, at 8:28 AM, Ian Hickson <ian at hixie.ch> wrote:
> 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!
Okay. If the only reason the current behavior exits was for backwards compatibility, the change works great for me.
- R. Niwa
More information about the whatwg