Thanks.

Ok, I'll extend the span, and will do Finch rollout after the partner's
experiment.
On Thu, Mar 20, 2025 at 12:36 AM Vladimir Levin <vmp...@chromium.org> wrote:

> 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
>
> On Wednesday, March 19, 2025 at 9:46:36 AM UTC-4 Stephen Chenney wrote:
>
>> 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?
>>
>>
>>>
>>>
>>>>
>>>> Thanks,
>>>> Vlad
>>>>
>>>> On Tuesday, March 18, 2025 at 8:32:23 PM UTC-4 Kent Tamura wrote:
>>>>
>>>>> Contact emailstk...@chromium.org
>>>>>
>>>>> Explainer
>>>>> https://docs.google.com/document/d/1UbHuoflNyLbSavpH86HEmXFGyz2V4uZ6cjNpuuwrtBg/edit?usp=sharing
>>>>>
>>>>> SpecificationNone
>>>>>
>>>>> 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 componentBlink>Canvas
>>>>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECanvas%22>
>>>>>
>>>>> Search tagscanvas <https://chromestatus.com/features#tags:canvas>
>>>>>
>>>>> TAG reviewNone
>>>>>
>>>>> TAG review statusNot 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
>>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>>>>> ?No
>>>>>
>>>>> Flag name on about://flagsNone
>>>>>
>>>>> Finch feature nameCanvasTextNg
>>>>>
>>>>> Requires code in //chrome?False
>>>>>
>>>>> Tracking bughttps://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
>>>>> <https://chromestatus.com/>.
>>>>>
>>>>>
>>>>> --
>>>>> TAMURA Kent
>>>>> Software Engineer, Google
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>> --
>>> TAMURA Kent
>>> Software Engineer, Google
>>>
>>>
>>> --
>>> 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+unsubscr...@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
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqG2J%3DJ%3D7Js28%2BwuzRHhjA-qHZ5%3DXYkZMGHDmZ-xoK2XTQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
TAMURA Kent
Software Engineer, Google

-- 
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+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqHLw%2B6t05r8ePH5Upjg-wn62m-4xaR8bmXt6NsgQSM-5Q%40mail.gmail.com.

Reply via email to