Intent to Experiment: Update of Canvas text rendering implementation

[TAMURA, Kent]

Contact emails

tk...@chromium.org

Explainer

https://docs.google.com/document/d/1UbHuoflNyLbSavpH86HEmXFGyz2V4uZ6cjNpuuwrtBg/edit?usp=sharing

Specification

None

Summary

This is not a web-exposed change. The implementation of CanvasRenderingContext2D's measureText(), fillText(), and strokeText() has a drastic change. This might affect performance, so we'd like to run an origin trial so canvas-heavy applications can try out the new implementation.

Blink component

Blink>Canvas

Search tags

canvas

TAG review

None

TAG review status

Not applicable

Risks

Interoperability and Compatibility

The feature might change performance characteristic, and might have performance regressions in some cases.

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None

Goals for experimentation

Ongoing technical constraints

None.

Debuggability

None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

No

Is this feature fully tested by web-platform-tests?

No

Flag name on about://flags

None

Finch feature name

CanvasTextNg

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/389726691

Estimated milestones

Origin trial desktop first	136
Origin trial desktop last	138
Origin trial Android first	136
Origin trial Android last	138
Origin trial WebView first	136
Origin trial WebView last	138

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5123274645962752?gate=5123363732979712

This intent message was generated by Chrome Platform Status.

--

TAMURA Kent
Software Engineer, Google

[Vladimir Levin]

I'm curious why you decided to do an origin trial instead of a more typical finch roll out + monitoring metrics for performance regressions. Origin trial data would limit us to the feedback of registered partners, which may not be a good representation of usage "in the wild". 

Separately, are you working with partners that are interested in registering for this already? I note that the request is for 2 milestones, which may be short if you don't already have partners lined up.

Thanks,

Vlad

[TAMURA, Kent]

On Wed, Mar 19, 2025 at 11:47 AM Vladimir Levin <vmp...@chromium.org> wrote:

I'm curious why you decided to do an origin trial instead of a more typical finch roll out + monitoring metrics for performance regressions. Origin trial data would limit us to the feedback of registered partners, which may not be a good representation of usage "in the wild". 

Separately, are you working with partners that are interested in registering for this already? I note that the request is for 2 milestones, which may be short if you don't already have partners lined up.

Yes, I already have a partner, and the partner asked us to set up an origin trial.  They want to run A/B testing in their application to check performance differences.

[Stephen Chenney]

On Wed, Mar 19, 2025 at 3:33 AM TAMURA, Kent <tk...@chromium.org> wrote:

On Wed, Mar 19, 2025 at 11:47 AM Vladimir Levin <vmp...@chromium.org> wrote:

I'm curious why you decided to do an origin trial instead of a more typical finch roll out + monitoring metrics for performance regressions. Origin trial data would limit us to the feedback of registered partners, which may not be a good representation of usage "in the wild". 

Separately, are you working with partners that are interested in registering for this already? I note that the request is for 2 milestones, which may be short if you don't already have partners lined up.

Yes, I already have a partner, and the partner asked us to set up an origin trial.  They want to run A/B testing in their application to check performance differences.

Would you then go with a Finch controlled general A/B test in M-138 or M-139? Are metrics in place to start getting baseline performance data?

 

--
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/CAGH7WqG2J%3DJ%3D7Js28%2BwuzRHhjA-qHZ5%3DXYkZMGHDmZ-xoK2XTQ%40mail.gmail.com.

[Vladimir Levin]

LGTM to experiment. One of the concerns is that 2 milestones may be too short of a duration for other partners to try this out.

So my approval extends to the standard 6 milestones (136 to 131 inclusive) and I encourage you to use more than 2 of those to gather data.

I also encourage you to roll out the change via finch when you decide to ship.

Thanks,

Vlad

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

[TAMURA, Kent]

Thanks.

Ok, I'll extend the span, and will do Finch rollout after the partner's experiment.

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/CAGH7WqG2J%3DJ%3D7Js28%2BwuzRHhjA-qHZ5%3DXYkZMGHDmZ-xoK2XTQ%40mail.gmail.com.