Closed Bug 289876 Opened 16 years ago Closed 9 years ago
support access Array element via () instead of  (IEism)
Assignee: general → robin.lu
Status: NEW → ASSIGNED
CC:ing to Boris.
This has come up before. I'd recommend reading existing bugs where this was proposed....
(In reply to comment #4) > existing bugs where this was proposed.... Bug 24644? And Bug 290592 is another enhancement? > Bug 24644 Implement E4X in SpiderMonkey > Bug 290592 Array extras: forEach, indexOf, filter, map, some, every
Correction of link to bug number. Sorry for spam. > Bug 246441 : Implement E4X in SpiderMonkey
No, the bugs were not related to E4X.
The w3c shut down the DOM working group. ECMA is never going to standardize this odious () for  VB-ism. So if we implement this, it will be because enough bad content exists that people want to work in Firefox and other Mozilla Gecko-based products, *and* that content's authors don't care or are not even around to fix it. I doubt that is the case. /be
(In reply to Brendan Eich [:brendan] from comment #8) > The w3c shut down the DOM working group. Browser competition led to the DOM core group being revived. But "caller" is deprecated. Cc'ing Cameron to confirm this resolution. > ECMA is never going to standardize this odious () for  VB-ism. That's still true. > So if we implement this, it will be because > enough bad content exists that people want to work in Firefox and other > Mozilla Gecko-based products, *and* that content's authors don't care > or are not even around to fix it. I doubt that is the case. No evidence of this, so WONTFIX. /be
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Yes, callers are deprecated. The keyword was changed to "legacycaller" to emphasise this, and the spec says explicitly Specifications SHOULD NOT use legacy callers unless required to specify the behavior of legacy APIs.
You need to log in before you can comment on or make changes to this bug.