Open
Bug 1020990
Opened 11 years ago
Updated 2 years ago
FileReader does not fire progress event at 100%
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: mozbz, Unassigned)
Details
Attachments
(1 file)
1018 bytes,
text/html
|
Details |
Firefox only emits Progress events until the file has been loaded, while Chromium and Internet Explorer emit Progress events up to and including 100%.
The W3C FileAPI spec specifies that a progress event must be fired "at 100% completion of the read operation" ( http://www.w3.org/TR/FileAPI/#events )
Not sure if a testcase is required, but have this anyway to clarify: this outputs the Loaded Bytes count of the last Progress Event received before the Load Event.
In Firefox, the result will be either 100% or less, depending on whether the whole file could be loaded at once.
I haven't yet received less than 100% in other browsers (expected behavior).
Comment 2•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•