[Bug 21811] New: [Custom]: Making HTMLElement the element interface of unresolved elements needs clarification

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

            Bug ID: 21811
           Summary: [Custom]: Making HTMLElement the element interface of
                    unresolved elements needs clarification
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: dominicc@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 14968

The spec says: "When an unresolved element is created, its element interface
must be: the HTMLElement, if the namespace is HTML Namespace;"

I think it would be appropriate to add commentary about the implications of
this for implementers, because the HTML spec says:

"The HTMLUnknownElement interface must be used for HTML elements that are not
defined by this specification (or other applicable specifications)."

Assuming a user agent treats Custom Elements as an applicable specification,
this means any element whose name is valid will now have HTMLElement and not
HTMLUnknownElement as an interface.

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

Received on Wednesday, 24 April 2013 13:12:59 UTC