W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

[Bug 27978] New: [Custom]: attachedCallback has no protocol for indicating that the custom tag is not applicable in this context

From: <bugzilla@jessica.w3.org>
Date: Sat, 07 Feb 2015 19:15:55 +0000
To: public-webapps@w3.org
Message-ID: <bug-27978-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27978

            Bug ID: 27978
           Summary: [Custom]: attachedCallback has no protocol for
                    indicating that the custom tag is not applicable in
                    this context
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: rjharmon0316+w3@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
            Blocks: 14968

I want to be able to call out cases where a custom tag has been used in a
context where it's just not applicable.  <tr> outside a <table> is a
traditional HTML example of this scenario, but we don't seem to have any
allowances for that scenario in the custom elements spec.

"attachedCallback
Unless specified otherwise, this callback must be enqueued whenever custom
element is inserted into a document and this document has a browsing context.
"

I was thinking that the component author should be able to raise an exception
from the attachedCallback to indicate that it's a wrong context for creating
the element.  Not that we can't console.log() to let component-users know about
the problem, but so that the user-agent can have the indication that the
element is invalid, perhaps triggering a visual treatment for the tag in
developer tools.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 7 February 2015 19:15:57 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC