[Bug 20913] [Custom]: What does inheriting from existing HTML element really mean?

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

--- Comment #31 from Anne <annevk@annevk.nl> ---
(In reply to comment #30)
> Do you see this as a dictionary argument for supplying element attribute
> values?

Nah, I thought just a simple string. createElement(localName [, customName]). A
better API for creating elements should not be created on top of createElement
I think, as it's pretty clear nobody really likes that API.


> Long term game plan is constructors. The mid-term dichotomy, however is
> somewhat maddening. I shudder imagining Web developer Bob trying to
> correctly determine how an element Foo should be constructed.

It can be much simpler than what you suggest. If it's a platform-defined
element, use createElement/createElementNS. If it's a custom element, use a
constructor.

Short term there will be libraries wrapping what we come up with no matter what
we do, as there will be implementation differences to paper over. Long term
still seems somewhat cloudy as to what the best way is to create a new element.

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

Received on Monday, 18 February 2013 10:05:21 UTC