Closed
Bug 742941
Opened 12 years ago
Closed 12 years ago
Restore an automated test for File objects
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
People
(Reporter: emk, Assigned: janv)
References
Details
No description provided.
Consensus on the WebApps list at W3C was that we didn't want to expose this to web pages. I.e. a File should always represent a real OS-file. But we can still expose this internally of we have APIs which need to instantiate File objects and return to webpages. But I think we might already have that.
Reporter | ||
Comment 2•12 years ago
|
||
I found |new File()|, but it looks to be only callable from chrome. test_file_cross_database_copying.html should be rewritten using xul.
Summary: Need an API to create File objects → Restore an automated test for File objects
Ah, indeed. I think we should keep that current setup.
Assignee | ||
Comment 4•12 years ago
|
||
I have a fix for this, it's a part of the patch for bug 726593. I added a new method to nsIDOMWindowUtils (to get a file object).
Assignee: nobody → Jan.Varga
Assignee | ||
Comment 5•12 years ago
|
||
fixed along with bug 726593
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Component: DOM: Mozilla Extensions → DOM
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•