Add support for the imageSmoothingQuality attribute on Paint Canvas. It allows a web developer to choose the quality/performance tradeoff when scaling images. There are 3 options in total for imageSmoothingQuality: low, medium and high. Chrome platform status entry for its launch on Canvas 2D: https://chromestatus.com/feature/4717415682277376
None
N/A
N/A
N/A
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
N/A
The Canvas 2D, Offscreen Canvas and Paint Canvas all share the same implementation for ImageSmoothingQuality property. This features has launched on Canvas 2D and Offscreen canvas for more than 8 years now. So the implementation has been well tested in stable.
Shipping on desktop | 133 |
Shipping on Android | 133 |
Shipping on WebView | 133 |
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
NoneSummary
Add support for the imageSmoothingQuality attribute on Paint Canvas. It allows a web developer to choose the quality/performance tradeoff when scaling images. There are 3 options in total for imageSmoothingQuality: low, medium and high. Chrome platform status entry for its launch on Canvas 2D: https://chromestatus.com/feature/4717415682277376
Is this feature fully tested by web-platform-tests?
No
It seems like perhaps the wrong feature type was selected, this
should really be an Intent to Ship. Fernando, do you mind
re-sending?
The ImageSmoothingQuality feature for Canvas 2D was launched in 2015, M54 (Chrome Status Link, original I2S). This feature was supposed to launch on Paint Canvas as well (Spec, precisely, the line "PaintRenderingContext2D includes CanvasImageSmoothing;"). However, we forgot to remove the flag in Paint Canvas when ImageSmoothingQuality was shipped. So this feature has been well used and tested in Canvas Rendering Context 2D in the past 9 years. That's why we set it as a "Web-Facing Change PSA".For tests: yes, Houtini features currently don't have to have web platform tests.
Yi XuOn Mon, Jan 6, 2025 at 4:44 PM Mike Taylor <mike...@chromium.org> wrote:On 1/6/25 3:37 PM, Noam Rosenthal wrote:
On Mon, Jan 6, 2025 at 7:01 PM Chromestatus <ad...@cr-status.appspotmail.com> wrote:
Summary
Add support for the imageSmoothingQuality attribute on Paint Canvas. It allows a web developer to choose the quality/performance tradeoff when scaling images. There are 3 options in total for imageSmoothingQuality: low, medium and high. Chrome platform status entry for its launch on Canvas 2D: https://chromestatus.com/feature/4717415682277376
Is this feature fully tested by web-platform-tests?
No
So houdini features don't go through I2S and don't come with web platform tests? Do they go through some other special process and have their own tests somewhere?
It seems like perhaps the wrong feature type was selected, this should really be an Intent to Ship. Fernando, do you mind re-sending?
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAC3hXJf%2BqmD7oikZC4qM7d4HXguzXg0pR0OocAgG65ueey295g%40mail.gmail.com.