[Bug 21817] New: [Custom]: Unresolved element interface must take type extensions into account

• From: <bugzilla@jessica.w3.org>
• Date: Wed, 24 Apr 2013 18:16:32 +0000
• To: public-webapps-bugzilla@w3.org
• Message-ID: <bug-21817-2532@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21817

            Bug ID: 21817
           Summary: [Custom]: Unresolved element interface must take type
                    extensions into account
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: dglazkov@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 18720

"When an unresolved element is created, its element interface must be:

the HTMLElement, if the namespace is HTML Namespace;
the SVGElement, if namespace is SVG Namespace; or"

This is not quite right. I should take type extensions into the account. For
<button is="foo-bar">, the element interface must be HTMLButtonElement.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 24 April 2013 18:16:37 UTC