Closed
Bug 403852
Opened 18 years ago
Closed 18 years ago
Unable to access nsIDOMFile using [] operator
Categories
(Core :: DOM: Core & HTML, defect, P4)
Tracking
()
RESOLVED
FIXED
People
(Reporter: BijuMailList, Assigned: dcamp)
References
Details
Attachments
(2 files)
1.14 KB,
patch
|
sicking
:
review+
sicking
:
superreview+
|
Details | Diff | Splinter Review |
2.23 KB,
patch
|
sicking
:
review+
sicking
:
superreview+
|
Details | Diff | Splinter Review |
see bug 371432
Unable to access nsIDOMFile by
document.getElementById('f').fileList[0]
as mentioned in bug 371432 Comment 62
or http://developer.mozilla.org/en/docs/nsIDOMFileList
and accessing using [] operator is common practice like
* arguments[]
* document.links[]
* selection.options[]
PS: I can get document.getElementById('f').fileList.item(0)
Comment 1•18 years ago
|
||
Probably just needs some DOMClassInfo love:
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/dom/src/base/nsDOMClassInfo.cpp&rev=1.491#7157
Should probably fix this before release. There is some classinfo love there, not sure what's missing.
It should be doable to write a mochitest for this actually, if you request UniversalXPConnect access you can set .value as you please. The tricky part would be finding what file-name to set :(
Assignee: nobody → dcamp
Flags: blocking1.9?
Comment 3•18 years ago
|
||
+'ing this and setting to P4 as there is a work around.
Flags: blocking1.9? → blocking1.9+
Priority: -- → P4
Assignee | ||
Comment 4•18 years ago
|
||
Attachment #293217 -
Flags: superreview?(jonas)
Attachment #293217 -
Flags: review?(jonas)
Assignee | ||
Comment 5•18 years ago
|
||
mochitest for the array syntax.
Attachment #293227 -
Flags: superreview?(jonas)
Attachment #293227 -
Flags: review?(jonas)
Comment on attachment 293217 [details] [diff] [review]
use ARRAY_SCRIPTABLE_FLAGS
Sweet
Attachment #293217 -
Flags: superreview?(jonas)
Attachment #293217 -
Flags: superreview+
Attachment #293217 -
Flags: review?(jonas)
Attachment #293217 -
Flags: review+
Comment on attachment 293227 [details] [diff] [review]
and a test
Technically, you don't need to do this from onload. You could just write the code inline and not bother with the SimpleTest.waitForExplicitFinish/finish fluff.
Attachment #293227 -
Flags: superreview?(jonas)
Attachment #293227 -
Flags: superreview+
Attachment #293227 -
Flags: review?(jonas)
Attachment #293227 -
Flags: review+
Assignee | ||
Comment 8•18 years ago
|
||
Checking in content/base/test/Makefile.in;
/cvsroot/mozilla/content/base/test/Makefile.in,v <-- Makefile.in
new revision: 1.37; previous revision: 1.36
done
RCS file: /cvsroot/mozilla/content/base/test/test_bug403852.html,v
done
Checking in content/base/test/test_bug403852.html;
/cvsroot/mozilla/content/base/test/test_bug403852.html,v <-- test_bug403852.html
initial revision: 1.1
done
Checking in dom/src/base/nsDOMClassInfo.cpp;
/cvsroot/mozilla/dom/src/base/nsDOMClassInfo.cpp,v <-- nsDOMClassInfo.cpp
new revision: 1.500; previous revision: 1.499
done
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 9•18 years ago
|
||
(In reply to comment #7)
> (From update of attachment 293227 [details] [diff] [review])
> Technically, you don't need to do this from onload. You could just write the
> code inline and not bother with the SimpleTest.waitForExplicitFinish/finish
> fluff.
I changed that.
Updated•18 years ago
|
Flags: in-testsuite+
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•