This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15019 - [Custom]: Specify a way to build UA HTML elements
Summary: [Custom]: Specify a way to build UA HTML elements
Status: RESOLVED LATER
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 15018 18511
  Show dependency tree / graph
 
Reported: 2011-11-30 17:38 UTC by Dimitri Glazkov
Modified: 2013-10-07 16:34 UTC (History)
2 users (show)

See Also:

Attachments

Description Dimitri Glazkov 2011-11-30 17:38:30 UTC 
Mozilla (and probably WebKit, too) is interested in building several (all?) HTML elements using the component model. Custom elements are a natural fit, though there are some things we must understand:

* how to distinguish in a non-error-prone way whether a custom element is built by UA or author.
* how to describe HTML elements as custom elements
Comment 1 Dominic Cooney 2012-05-22 01:47:27 UTC 
(In reply to comment #0)
> Mozilla (and probably WebKit, too) is interested in building several (all?)
> HTML elements using the component model. Custom elements are a natural fit,
> though there are some things we must understand:
> 
> * how to distinguish in a non-error-prone way whether a custom element is built
> by UA or author.

Can you elaborate what you mean by "built by"? Do you mean "instantiated by" or "defined by"? Why do you want to distinguish this?

> * how to describe HTML elements as custom elements

It seems that the UA might want to have a sanctified place to process <element> elements that permits naming non-HTML elements to bootstrap the definitions, eg.

<element name="body" extends="~*magic*~">…