Skip to content
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

Reacting to environment changes doesn't fire loadstart or loadend events #3860

Closed
jdm opened this issue Jul 30, 2018 · 2 comments · Fixed by #4842
Closed

Reacting to environment changes doesn't fire loadstart or loadend events #3860

jdm opened this issue Jul 30, 2018 · 2 comments · Fixed by #4842

Comments

@jdm
Copy link
Member

jdm commented Jul 30, 2018

It's not clear if it's intentional or desirable to have this difference between the regular "update the image data" algorithm and the one that runs in reaction to the environment changing.

@jdm
Copy link
Member Author

jdm commented Jul 30, 2018

cc @zcorpan

@annevk
Copy link
Member

annevk commented Aug 9, 2018

See also #3709.

annevk added a commit that referenced this issue Aug 16, 2019
It seems this feature got added without an agreed upon plan. Firefox fires the loadstart event, but I cannot find evidence of the other events or them using the correct class.

Tests: ...

Closes #1915. Closes #3860.
annevk added a commit that referenced this issue Aug 20, 2019
It seems this feature got added without an agreed upon plan. Firefox fires the loadstart event, but I cannot find evidence of the other events or them using the correct class.

Tests: web-platform-tests/wpt#18499.

Closes #1915. Closes #3860.
zcorpan pushed a commit that referenced this issue Nov 6, 2019
It seems this feature got added without an agreed upon plan. Firefox fires the loadstart event, but I cannot find evidence of the other events or them using the correct class.

Tests: web-platform-tests/wpt#18499.

Closes #1915. Closes #3860.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants