This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html Multipage: http://www.whatwg.org/C#global-attributes Complete: http://www.whatwg.org/c#global-attributes Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html Comment: there is no IDL dom attribute for inert state of element Posted from: 95.84.151.114 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.72 Safari/537.36
What's the use case?
May be for custom html widgets, which might be disabled programmatically (actually be inert), instead of manually prevent events to be fired on what elements. Example: MyCustomControl.disabled = function() { this.element.inert = true; } MyCustomControl.disable(); If you meant why "inert" attribute should have corresponding DOM idl property of element, then I should ask--why other attributes have? P.S. Sorry for anonymous bug report.
Oh you mean a reflection attribute for the content attribute, not an attribute that reports the current state, I see. My apologies. Yeah, not having that is just an oversight, my bad.
Checked in as WHATWG revision r8140. Check-in comment: HTMLElement.inert IDL attribute http://html5.org/tools/web-apps-tracker?from=8139&to=8140
I was glad to help :)
Checked in as WHATWG revision r8144. Check-in comment: Ack for r8140 http://html5.org/tools/web-apps-tracker?from=8143&to=8144