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 28121 - The concept of creators has been removed from WebIDL; setters are always also creators
Summary: The concept of creators has been removed from WebIDL; setters are always also...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: https://html.spec.whatwg.org/#the-dom...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-01 16:38 UTC by contributor
Modified: 2015-09-01 07:35 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2015-03-01 16:38:24 UTC 
Specification: https://html.spec.whatwg.org/
Multipage: https://html.spec.whatwg.org/multipage/#the-domstringmap-interface
Complete: https://html.spec.whatwg.org/#the-domstringmap-interface
Referrer: https://codereview.chromium.org/972493002/

Comment:
The concept of creators has been removed from WebIDL; setters are always also
creators

Posted from: 14.162.102.1
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36 OPR/27.0.1689.76
Comment 1 Philip Jägenstedt 2015-03-01 16:39:58 UTC 
The creator keyword is used on DOMStringMap and multiple other interfaces.

https://heycam.github.io/webidl/ say "Removed the concept of creators; setters are always also creators."
Comment 2 Ian 'Hixie' Hickson 2015-03-04 21:47:42 UTC 
Um, interesting. So now setters have to check if the property doesn't exist, and throw an exception if it doesn't? (Unless you also want a creator.)
Comment 3 Philip Jägenstedt 2015-03-05 07:15:02 UTC 
AFAICT all the setters in HTML are also creators, so that shouldn't matter?

But CC Cameron McCormack, I could be completely confused :)
Comment 4 Ian 'Hixie' Hickson 2015-03-30 22:22:36 UTC 
Yeah, this isn't a problem for any HTML setters (other than just being spec churn in general).