This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23451 - Error Attribute Setting and Error Event Firing Currently Have Backwards Order
Summary: Error Attribute Setting and Error Event Firing Currently Have Backwards Order
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: File API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Arun
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-07 18:05 UTC by Arun
Modified: 2013-10-31 17:08 UTC (History)
1 user (show)

See Also:

Attachments

Description Arun 2013-10-07 18:05:17 UTC 
On listserv traffic to public-webapps, brmatthe points out:

File API: 8.5.6 step 1 in the spec starts "Fire a progress event called error. Set the error attribute;". Doesn't firing an event call the event handlers immediately? If so, this seems to be saying to call the error handler *before* setting the error attribute,  which seems backwards.

Expected: event and event attribute setting are not backwards.