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

[Bug 27976] New: [Custom]: type extensions should be available as custom tags, not only through <baseTag is="...">

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

            Bug ID: 27976
           Summary: [Custom]: type extensions should be available as
                    custom tags, not only through <baseTag is="...">
           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

It seems to me that it's unnecessarily limiting to require that users specify
the base tag type and also the extension tag.  It seems to prevent the direct
use of semantic tags which happen to use a non-generic html tag prototype.

This might be simply a clarity issue, where in 11.2 Type Extension Example, you
could specify that <button is=tequila-button> is equivalent to
<tequila-button>.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 7 February 2015 18:52:04 UTC

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