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

[Bug 18710] New: [Templates]: Trigger parse errors when template content does not match the template context.

From: <bugzilla@jessica.w3.org>
Date: Mon, 27 Aug 2012 18:59:33 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-18710-2532@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18710

           Summary: [Templates]: Trigger parse errors when template
                    content does not match the template context.
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
        AssignedTo: dglazkov@chromium.org
        ReportedBy: tross@microsoft.com
         QAContact: public-webapps-bugzilla@w3.org
            Blocks: 15476


Functionally we want templates to be declared anywhere and be able to declare
anything. That said, I suspect this behavior could confuse some authors who
mistakenly put content in a template that would normally be inappropriate for
the context in which the template has been declared (e.g.
<table><template><div>).

To help authors identify these scenarios (which are likely mistakes), I suggest
we consider including context-sensitive parse errors. Functionally everything
would still parse the same, but we would trigger an error for unexpected
content (like <table><template><div>). We would not trigger these new errors
for templates declared within <head> regardless of content.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 27 August 2012 18:59:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 August 2012 18:59:36 GMT