15019 2011-11-30 17:38:30 +0000 [Custom]: Specify a way to build UA HTML elements 2013-10-07 16:34:51 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED LATER P2 normal --- 15018 18511 1 dglazkov dglazkov dominicc jonas public-webapps-bugzilla oldest_to_newest 60689 0 dglazkov 2011-11-30 17:38:30 +0000 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 67987 1 dominicc 2012-05-22 01:47:27 +0000 (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*~">…