-
Notifications
You must be signed in to change notification settings - Fork 33
Non-responsive image loading #195
Description
Description
This investigate area will look at what's required to specify image loading that's compatible with web content.
Rationale
Updating gecko to match the spec for loading caused some test failures that pointed to likely webcompat regressions that prevented the patches from landing.
In particular, tests under https://github.com/web-platform-tests/wpt/tree/master/html/canvas/element/drawing-images-to-the-canvas broke when implementing the spec as written. After some investigation and an attempt to "fix" the tests in web-platform-tests/wpt#5060 it was decided that the spec is too different to existing behavior when setting the src attribute for it to be implementable.
The current status of the issue is recorded in various bugs and spec issues:
https://bugzilla.mozilla.org/show_bug.cgi?id=1076583
whatwg/html#2429
whatwg/html#4884
whatwg/html#1872
Having a usable specification of fundamental platform features is required to avoid compat hazards and ensure that all implementations are able to converge on the same behaviour. It also opens the door to confidently adding future functionality without worrying that differences between the spec and implementations may lead to problems when it comes to shipping the features.
Investigation Roadmap
- Write test cases to cover edge cases of image loading, including observed regressions from implementing the current spec.
- Run the tests cross-browser to find existing areas of difference.
- Agree on a model and use it to derive "correct" behaviour for each test.
- Use telemetry, archive crawls, experimental implementation, etc. to provide supporting data for the web compatibility of the proposed model.
- Write up the proposal as a PR to the HTML spec.