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 22392 - maybe define .name for Function objects corresponding to operations/attributes
Summary: maybe define .name for Function objects corresponding to operations/attributes
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL: http://wiki.ecmascript.org/doku.php?i...
Whiteboard: [v1]
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-17 21:52 UTC by Cameron McCormack
Modified: 2016-01-04 23:34 UTC (History)
6 users (show)

See Also:

Attachments

Description Cameron McCormack 2013-06-17 21:52:22 UTC 
It sounds like ES might define .name on functions at some point, so we probably want to define what its value is for the Function objects we have for operations, attribute getters/setters, etc.
Comment 1 Brendan Eich 2013-06-18 00:37:25 UTC 
The name property of function objects is being standardized in ES6. See this bug's URL.

/be
Comment 2 Cameron McCormack 2013-06-18 00:46:02 UTC 
Thanks for the link.  I'll follow the patterns on that page.
Comment 3 Boris Zbarsky 2013-06-18 02:15:28 UTC 
So if I read that right, that would make document.querySelector.name == "querySelector" and the innerHTML accessors would have "get innerHTML" and "set innerHTML" as the name?
Comment 4 Rick Waldron 2013-06-18 02:41:07 UTC 
Bori(In reply to comment #3)
> So if I read that right, that would make document.querySelector.name ==
> "querySelector" and the innerHTML accessors would have "get innerHTML" and
> "set innerHTML" as the name?

Correct!