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 26643 - Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
Summary: Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an...
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-22 18:13 UTC by Olli Pettay
Modified: 2015-07-06 08:18 UTC (History)
4 users (show)

See Also:


Attachments

Comment 1 Boris Zbarsky 2014-08-22 18:49:36 UTC
Where is this reflection mode actually used?
Comment 2 Olli Pettay 2014-08-22 19:07:48 UTC
Label element seems to use it.
Comment 3 Boris Zbarsky 2014-08-22 19:54:54 UTC
Where?  HTMLLabelElement has three IDL attributes, only one of which relects a content attribute.  And that one is a string.
Comment 4 Anne 2014-08-25 09:59:04 UTC
contextMenu is a property with a setter where this reflection mode is fully used.
Comment 5 Boris Zbarsky 2014-08-25 13:26:43 UTC
Does anyone implement it, or plan to?
Comment 6 Olli Pettay 2014-08-25 14:13:26 UTC
(In reply to Boris Zbarsky from comment #3)
> Where?  HTMLLabelElement has three IDL attributes, only one of which relects
> a content attribute.  And that one is a string.

Oh, right. form attribute isn't using this stuff but has explicit
"If a reassociateable form-associated element has a form attribute specified, then that attribute's value must be the ID of a form element in the element's owner Document."
Comment 7 Boris Zbarsky 2014-08-25 14:16:25 UTC
Right, so there is the question of how http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#reset-the-form-owner should work with web components, which probably needs a separate spec bug.  Right now as specced @form simply doesn't work at all inside a component.
Comment 8 Olli Pettay 2014-08-25 14:24:30 UTC
Bug 26656
Comment 9 Hayato Ito 2015-07-06 08:18:44 UTC
Moved to https://github.com/w3c/webcomponents/issues/199