Closed
Bug 738193
Opened 13 years ago
Closed 13 years ago
'for (x of foo.childNodes)' sometimes yields enumerable property names instead of iterable properties
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox13 | - | --- |
People
(Reporter: dao, Unassigned)
References
Details
STR:
With this bugzilla page opened, open the error console and evaluate this:
[x for (x of top.opener.content.document.body.childNodes)]
expected:
[object Text],[object HTMLDivElement],[object Text],[object HTMLDivElement],[object Text],[object HTMLDivElement],[object Text],[object HTMLScriptElement],[object Text],[object HTMLScriptElement],[object Text],[object HTMLScriptElement],[object Text],[object HTMLElement],[object Text]
actual result:
0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,length,item
Reporter | ||
Updated•13 years ago
|
Severity: normal → major
![]() |
||
Comment 1•13 years ago
|
||
Is this just an issue with XrayWrapper?
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to Boris Zbarsky (:bz) from comment #1)
> Is this just an issue with XrayWrapper?
That would match what I'm seeing.
Reporter | ||
Comment 3•13 years ago
|
||
[x for (x of top.opener.content.document.body.wrappedJSObject.childNodes)] works as expected.
Comment 4•13 years ago
|
||
Triage question: Dão, how high priority is 737792 for you?
Reporter | ||
Comment 5•13 years ago
|
||
Bug 737792 isn't a priority. I nominated this because I wasn't sure if this could affect web content. If it can't, it probably doesn't need to be fixed immediately, although it would be nice for chrome JS (Firefox, add-ons, etc.).
Comment 6•13 years ago
|
||
(In reply to Dão Gottwald [:dao] from comment #5)
> Bug 737792 isn't a priority. I nominated this because I wasn't sure if this
> could affect web content. If it can't, it probably doesn't need to be fixed
> immediately, although it would be nice for chrome JS (Firefox, add-ons,
> etc.).
Thanks. It's not a standard yet, and it shouldn't affect web content, so I won't bother release drivers with it. I think it's still a relatively high priority for us (unless Jason has a different opinion), because we do want for-of to work correctly and developers to experiment with it.
Reporter | ||
Comment 7•13 years ago
|
||
It looks like this got fixed by some other bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Updated•13 years ago
|
Flags: in-testsuite?
Reporter | ||
Updated•11 years ago
|
Flags: in-testsuite?
You need to log in
before you can comment on or make changes to this bug.
Description
•