W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

[Bug 20130] New: [Templates]: <template> within <template> effectively resets the implied context

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Nov 2012 19:22:12 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20130-2532@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20130

            Bug ID: 20130
           Summary: [Templates]: <template> within <template> effectively
                    resets the implied context
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: rafaelw@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 15476

e.g. 

#data
<body><template><tr></tr><template></template><td></td></template>
#errors
#document
| <html>
|   <head>
|   <body>
|     <template>
|       #document-fragment
|         <tr>
|         <template>
|           #document-fragment
|         <td>

I actually don't have an opinion as to whether this is a bug, I just wanted to
call it out (and I'm including the above in the initial webkit patch).

In order to enforce a *single* implied context, a stack of
template->contextTagNames would need to be kept along side the stack of open
elements.

I kind of feel like its added complexity and there's no obvious harm to the
above behavior.

Opinions?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 28 November 2012 19:22:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 November 2012 19:22:18 GMT