Restore an automated test for File objects

RESOLVED FIXED

Status

()

Core
DOM
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: emk, Assigned: janv)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Comment hidden (empty)
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

6 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

5 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

5 years ago
fixed along with bug 726593
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: DOM: Mozilla Extensions → DOM
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.