-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Add more tests for FileReader.result. #7494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more tests for FileReader.result. #7494
Conversation
Build BROKENStarted: 2017-09-26 20:43:16 Failing Jobs
View more information about this build on: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry about the delay - is this still valid?
In particular this adds tests to verify the value of the attribute during progress and loadstart events.
4ba45d9
to
6625a32
Compare
Sorry about the delay, yes this is still valid. These are tests for the spec changes in w3c/FileAPI#118 |
reader[method](blob); | ||
assert_equals(reader.result, null, 'result is null after first read call'); | ||
await eventWatcher.wait_for(event); | ||
assert_equals(reader.result, null, 'result is null during event'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice... and all browsers have converged on including the microtask execution within the event dispatch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
In particular this adds tests to verify the value of the attribute during progress and loadstart events.
In particular this adds tests to verify the value of the attribute
during progress and loadstart events.
I think this matches what the spec currently says, but there are some open questions in w3c/FileAPI#79 about what the spec should actually say, so we should probably not merge this until we figure out what the desired behavior actually is.