On 3/12/25 5:38 PM, Frank Tang (譚永鋒) wrote:
On Wed, Mar 12, 2025 at 8:19 AM Chris Harrelson
wrote:
On Wed, Mar 5, 2025 at 10:39 AM 'Frank Tang (譚永鋒)' via blink-dev
wrote:
On Wed, Mar 5, 2025 at 6:02 AM Daniel Bratell
wrote:
Looks like the use cou
On Wed, Mar 12, 2025 at 4:22 PM 'Panos Astithas' via blink-dev <
blink-dev@chromium.org> wrote:
> On Wed, Mar 12, 2025 at 3:12 PM Mike Taylor
> wrote:
>
>> On 3/12/25 5:38 PM, Frank Tang (譚永鋒) wrote:
>>
>>
>>
>> On Wed, Mar 12, 2025 at 8:19 AM Chris Harrelson
>> wrote:
>>
>>>
>>>
>>> On Wed, Mar
On Wed, Mar 12, 2025 at 3:12 PM Mike Taylor wrote:
> On 3/12/25 5:38 PM, Frank Tang (譚永鋒) wrote:
>
>
>
> On Wed, Mar 12, 2025 at 8:19 AM Chris Harrelson
> wrote:
>
>>
>>
>> On Wed, Mar 5, 2025 at 10:39 AM 'Frank Tang (譚永鋒)' via blink-dev <
>> blink-dev@chromium.org> wrote:
>>
>>>
>>>
>>> On Wed,
On Wed, Mar 5, 2025 at 10:39 AM 'Frank Tang (譚永鋒)' via blink-dev <
blink-dev@chromium.org> wrote:
>
>
> On Wed, Mar 5, 2025 at 6:02 AM Daniel Bratell wrote:
>
>> Looks like the use counter LocaleInfoObsoleteGetters is at 0.033% which
>> is a bit high.
>>
> Dear Daniel:
>
> From your point of view
On Wed, Mar 12, 2025 at 8:19 AM Chris Harrelson
wrote:
>
>
> On Wed, Mar 5, 2025 at 10:39 AM 'Frank Tang (譚永鋒)' via blink-dev <
> blink-dev@chromium.org> wrote:
>
>>
>>
>> On Wed, Mar 5, 2025 at 6:02 AM Daniel Bratell
>> wrote:
>>
>>> Looks like the use counter LocaleInfoObsoleteGetters is at 0.
On Wed, Mar 5, 2025 at 6:02 AM Daniel Bratell wrote:
> Looks like the use counter LocaleInfoObsoleteGetters is at 0.033% which is
> a bit high.
>
Dear Daniel:
>From your point of view, could you please define what number would
be considered as not "high" or "low enough" ?
>
I can't see LocaleI
Looks like the use counter LocaleInfoObsoleteGetters is at 0.033% which
is a bit high. I can't see LocaleInfoFunctions at all so does that mean
that it has never been triggered?
/Daniel
On 2024-11-14 15:31, Mike Taylor wrote:
Thanks Frank.
4% as an upper bound is a very, very large number,
Thanks Frank.
4% as an upper bound is a very, very large number, so I think we should
wait until we have proper UseCounter data for each of the getters to
better understand the compatibility risk.
On 11/13/24 6:11 PM, 'Frank Tang (譚永鋒)' via blink-dev wrote:
I added a cl
https://chromium-revi
I added a cl
https://chromium-review.googlesource.com/c/chromium/src/+/6020626 to add
the counter. The first half of instrumenting the v8 code is done in 2023
but somehow I forgot to add them to the blink code.
On Wed, Nov 13, 2024 at 1:29 PM Frank Tang (譚永鋒) wrote:
>
>
> On Wed, Nov 13, 2024 at
On Wed, Nov 13, 2024 at 8:42 AM Daniel Bratell wrote:
> Is this request to just deprecate them or is it to remove them as well,
> right away or at a future set date?
>
The request is to remove the getters, which is removed from the proposed
spec a while back.
These getters were never part of the
Is this request to just deprecate them or is it to remove them as well,
right away or at a future set date?
Secondly, you say usage is low, which makes a lot of sense, but do we
know how low? Are there Use Counters or some other hard number we can
lean on?
/Daniel
On 2024-11-12 21:34, Chrom
Contact emails
ft...@google.com
Explainer
None
Specification
https://tc39.es/proposal-intl-locale-info
Design docs
https://docs.google.com/document/d/1BSpa-LKE69LL1g5CHZ3G06XEfffauwS24atfSUQiIDY/edit
Summary
Intl Locale Info API is a Stage 3 ECMAScript TC39 proposal to enhance the
Intl.L
12 matches
Mail list logo
