- From: Ryosuke Niwa <rniwa@apple.com>
- Date: Tue, 03 Dec 2013 12:56:44 -0800
- To: whatwg Group <whatwg@lists.whatwg.org>
On Dec 3, 2013, at 10:42 AM, Adam Barth <abarth@eecs.berkeley.edu> wrote: > Did you mean to drop whatwg from the CC list? > > On Tue, Dec 3, 2013 at 10:39 AM, Ian Hickson <ian@hixie.ch> wrote: >> On Thu, 21 Nov 2013, Ryosuke Niwa wrote: >>> >>> A start tag whose tag name is "isindex" >>> http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#isindex >>> >>> Right now, form element pointer is not null in the following example, so we end up losing isindex element entirely. >>> <!DOCTYPE html> >>> <html><body><form><template>a<isindex></isindex>b</template> >> >> 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. > > That seems bad for authors because I can imagine folks wanting to have > a templated form. :) > >> Or, we could have a form element pointer stack that parallels the >> template stack. >> >> I guess the latter is best for authors. How do implementors feel about >> adding a new stack for the template stuff? 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? - R. Niwa
Received on Tuesday, 3 December 2013 20:57:08 UTC