24102 – Specify the targets for events

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 24102 - Specify the targets for events

Summary: Specify the targets for events

Status:	RESOLVED FIXED

Alias:	None

Product:	WebAppsWG
Classification:	Unclassified
Component:	File API (show other bugs)
Version:	unspecified
Hardware:	All All

Importance:	P2 normal
Target Milestone:	---
Assignee:	Arun
QA Contact:	public-webapps-bugzilla

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2013-12-15 10:28 UTC by Ms2ger
Modified:	2014-02-27 22:51 UTC (History)
CC List:	2 users (show)

See Also:

Attachments

Description Ms2ger 2013-12-15 10:28:48 UTC

For example, in readAsText:

"Fire a progress event called loadstart."

Nothing actually defines that the event is fired at the FileReader object. (Consider using the term 'context object' to match DOM.)

Comment 1 Arun 2013-12-24 11:47:56 UTC

(In reply to Ms2ger from comment #0)
> For example, in readAsText:
> 
> "Fire a progress event called loadstart."
> 
> Nothing actually defines that the event is fired at the FileReader object.
> (Consider using the term 'context object' to match DOM.)

I don't agree.  http://dev.w3.org/2006/webapi/FileAPI/#blobreader-task-source

Comment 2 Arun 2014-01-21 16:11:44 UTC

Marking this bug closed, since there isn't a response to Comment 1.

Comment 3 Anne 2014-01-21 16:44:08 UTC

Reopening. A task source is not an event target. You should probably introduce an IO task source for tasks. The event target should be the FileReader object (at least for the events dispatched to it).

Comment 4 Arun 2014-02-27 22:51:28 UTC

I think this is fixed. Relevant fixes include:

1. http://dev.w3.org/2006/webapi/FileAPI/#fire-a-progress-event

2. All the asynch read methods:
http://dev.w3.org/2006/webapi/FileAPI/#readAsDataURL
http://dev.w3.org/2006/webapi/FileAPI/#readAsDataText
http://dev.w3.org/2006/webapi/FileAPI/#readAsArrayBuffer