date:20170912

Re: [blink-dev] Re: [v8-users] Intent to Ship: Intl.PluralRules

2017-09-12 Thread Adam Klein

Thanks, with that background this LGTM to ship.

On Tue, Sep 12, 2017 at 2:35 PM, Daniel Ehrenberg 
wrote:

> I asked Zbigniew Braniecki about the status of
> Intl.NumberFormat.prototype.formatToParts and PluralRules, and he told
> me,
>
> > Both are ready and need to be exposed. We've been waiting for them to
> reach stage 4 to expose them to the Web
> > NumberFormat.formatToParts is behind the flag -
> http://searchfox.org/mozilla-central/source/js/src/builtin/Intl.cpp#1639
> > and PluralRules is exposed on mozIntl (which is our chrome-only API for
> UI internationalization that extends Intl API) -
> http://searchfox.org/mozilla-central/source/toolkit/
> components/mozintl/mozIntl.js#73
> > With you guys having land both I think we can expose them now. I'm happy
> to work on the patch next week :)
>
> In particular, Mozilla has been pushing these proposals for some time,
> and has been held back by lack of buy-in from other browser vendors.
>
> Dan
>
> On Tue, Sep 12, 2017 at 9:45 AM,   wrote:
> > This implementation is for SpiderMoneky shell only with
> addIntlExtras(Intl).
> > It isn't available on Gecko yet.
> >
> > -- Makoto Kato
> >
> > 2017年9月12日火曜日 6時30分27秒 UTC+9 Adam Klein:
> >>
> >> Thanks, from the spec-stabilization side this sounds fine to me.
> >>
> >> Given that we'd be first to ship, I wonder if you have any more
> background
> >> on the Firefox status: the intent lists it as "in development" there,
> but
> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1270146 has been closed,
> and
> >> says it's "Fixed in Firefox 53". But I'm running Firefox 55 locally and
> I
> >> don't see it shipped there.
> >>
> >> On Sun, Sep 10, 2017 at 10:17 AM, Daniel Ehrenberg <
> litt...@chromium.org>
> >> wrote:
> >>>
> >>> +blink-dev
> >>>
> >>> On Sun, Sep 10, 2017 at 7:16 PM, Daniel Ehrenberg
> >>>  wrote:
> >>> > ECMA 402 (Intl) tracks its proposals separately. You can see it
> listed
> >>> > as Stage 3 at https://github.com/tc39/ecma402/ . There is a full
> >>> > implementation in Firefox behind a flag. I'd say this spec is pretty
> >>> > stable.
> >>> >
> >>> > Dan
> >>> >
> >>> > On Fri, Sep 8, 2017 at 7:39 PM, Adam Klein 
> wrote:
> >>> >> What's the stability state of the spec? I don't see it on
> >>> >> https://github.com/tc39/proposals
> >>> >>
> >>> >> On Fri, Sep 8, 2017 at 9:41 AM, Josh Wolfe 
> wrote:
> >>> >>>
> >>> >>> # Contact emails
> >>> >>>
> >>> >>> jwo...@igalia.com
> >>> >>> litt...@chromium.org
> >>>
> >>> >>>
> >>> >>> # Spec
> >>> >>>
> >>> >>> https://rawgit.com/caridy/intl-plural-rules-spec/master/index.html
> >>> >>>
> >>> >>> # Summary
> >>> >>>
> >>> >>> Intl.PluralRules is a new API which exposes language-dependent data
> >>> >>> on
> >>> >>> pluralization forms of numbers. Given a locale and a number,
> >>> >>> Intl.PluralRules outputs a category, which can then be used for
> >>> >>> selection of the pluralization form of surrounding text.
> >>> >>>
> >>> >>> # Motivation
> >>> >>>
> >>> >>> In English, 101st ends with "st" while 111th ends with "th". The
> >>> >>> algorithm
> >>> >>> for
> >>> >>> determining the proper ordinal suffix is non-trivial and locale
> >>> >>> specific.
> >>> >>> A
> >>> >>> proper international solution is implemented in ICU, and
> >>> >>> Intl.PluralRules
> >>> >>> exposes this solution to JavaScript developers.
> >>> >>>
> >>> >>> # Interoperability risk
> >>> >>>
> >>> >>> * Firefox: In development
> >>> >>> * Edge: No public signals
> >>> >>> * Safari: No public signals
> >>> >>> * Web developers: Positive
> >>> >>>
> >>> >>> # Compatibility risk
> >>> >>>
> >>> >>> Low compatibility risk, as this feature is exposed through a new
> >>> >>> field
> >>> >>> `Intl.PluralRules`.
> >>> >>>
> >>> >>> # Ongoing technical constraints
> >>> >>>
> >>> >>> None
> >>> >>>
> >>> >>> # Will this feature be supported on all six Blink platforms
> (Windows,
> >>> >>> Mac,
> >>> >>> Linux, Chrome OS, Android, and Android WebView)?
> >>> >>>
> >>> >>> Yes
> >>> >>>
> >>> >>> # OWP launch tracking bug
> >>> >>>
> >>> >>> https://bugs.chromium.org/p/v8/issues/detail?id=5601
> >>> >>>
> >>> >>> # Link to entry on the Chrome Platform Status
> >>> >>>
> >>> >>> https://www.chromestatus.com/features/5653874773852160
> >>> >>>
> >>> >>> --
> >>> >>> --
> >>> >>> v8-users mailing list
> >>> >>> v8-u...@googlegroups.com
> >>> >>> http://groups.google.com/group/v8-users
> >>> >>> --- You received this message because you are subscribed to the
> >>> >>> Google
> >>> >>> Groups "v8-users" group.
> >>> >>> To unsubscribe from this group and stop receiving emails from it,
> >>> >>> send an
> >>> >>> email to v8-users+u...@googlegroups.com.
> >>> >>> For more options, visit https://groups.google.com/d/optout.
> >>> >>
> >>> >>
> >>> >> --
> >>> >> --
> >>> >> v8-users mailing list
> >>> >> v8-u...@googlegroups.com
> >>> >> http://groups.google.com/group/v8-users
>

Re: [blink-dev] Re: [v8-users] Intent to Ship: Intl.NumberFormat.prototype.formatToParts

2017-09-12 Thread Adam Klein

Thanks, with that background this LGTM to ship.

On Tue, Sep 12, 2017 at 2:35 PM, Daniel Ehrenberg 
wrote:

> I asked Zbigniew Braniecki about the status of
> Intl.NumberFormat.prototype.formatToParts and PluralRules, and he told
> me,
>
> > Both are ready and need to be exposed. We've been waiting for them to
> reach stage 4 to expose them to the Web
> > NumberFormat.formatToParts is behind the flag -
> http://searchfox.org/mozilla-central/source/js/src/builtin/Intl.cpp#1639
> > and PluralRules is exposed on mozIntl (which is our chrome-only API for
> UI internationalization that extends Intl API) -
> http://searchfox.org/mozilla-central/source/toolkit/
> components/mozintl/mozIntl.js#73
> > With you guys having land both I think we can expose them now. I'm happy
> to work on the patch next week :)
>
> In particular, Mozilla has been pushing these proposals for some time,
> and has been held back by lack of buy-in from other browser vendors.
>
> Dan
>
> On Mon, Sep 11, 2017 at 11:32 PM, Adam Klein  wrote:
> > I have the same question here as my latest question on the PluralRules
> > thread: any idea why Firefox isn't shipping this (yet), given they have
> it
> > implemented?
> >
> > On Sun, Sep 10, 2017 at 2:03 PM, Josh Wolfe  wrote:
> >>
> >> # Contact emails
> >>
> >> jwo...@igalia.com
> >> little...@chromium.org
> >>
> >> # Spec
> >>
> >> https://github.com/tc39/ecma402/pull/79
> >>
> >> # Summary
> >>
> >> Intl.NumberFormat.prototype.formatToParts() is scheduled to be added to
> >> the
> >> EcmaScript Internationalization API specification (Ecma 402). It adds a
> >> method
> >> to format a number to a list of tokens and their types (e.g. minusSign,
> >> integer,
> >> decimal, fraction, currency, percentSign, etc). It is implemented and
> >> disabled
> >> by default by Firefox. v8 implemented it behind a flag. See also, the
> >> corresponding DateTimeFormat feature here:
> >> https://www.chromestatus.com/feature/6319456309477376
> >>
> >> # Motivation
> >>
> >> A web form may want to display a price like "$1,234.00" with the
> >> fractional
> >> part ".00" in superscript and in a different color. If you use
> >> Intl.NumberFormat.prototype.format(), you get a string, which you would
> >> then
> >> need to parse to find the fractional part. However, the decimal
> separator
> >> is
> >> locale dependent, so attempting to account for this variability somewhat
> >> defeats the purpose of the locale-independent NumberFormat API. The
> >> solution is
> >> to expose the individual parts of the formatted string with tags to
> >> identify
> >> each part's role in the overall representation.
> >>
> >> # Interoperability risk
> >>
> >> * Firefox: In development
> >> * Edge: No public signals
> >> * Safari: No public signals
> >> * Web developers: No signals
> >>
> >> # Compatibility risk
> >>
> >> Low compatibility risk, as this feature is exposed through a new method
> >> `Intl.NumberFormat.prototype.formatToParts`.
> >>
> >> # Ongoing technical constraints
> >>
> >> None
> >>
> >> # Will this feature be supported on all six Blink platforms (Windows,
> Mac,
> >> Linux, Chrome OS, Android, and Android WebView)?
> >>
> >> Yes
> >>
> >> # OWP launch tracking bug
> >>
> >> https://bugs.chromium.org/p/v8/issues/detail?id=5244
> >>
> >> # Link to entry on the Chrome Platform Status
> >>
> >> https://www.chromestatus.com/feature/5686840812109824
> >>
> >> --
> >> --
> >> v8-users mailing list
> >> v8-users@googlegroups.com
> >> http://groups.google.com/group/v8-users
> >> --- You received this message because you are subscribed to the Google
> >> Groups "v8-users" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to v8-users+unsubscr...@googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> >
> > --
> > --
> > v8-users mailing list
> > v8-users@googlegroups.com
> > http://groups.google.com/group/v8-users
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "v8-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to v8-users+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To view this discussion on the web visit https://groups.google.com/a/
> chromium.org/d/msgid/blink-dev/CAKtSNYMPZe0y3M0%2BFWi%3DOzZskMBaqLPro%
> 3DrnfubC7emyUzHqNw%40mail.gmail.com.
>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [blink-dev] Re: [v8-users] Intent to Ship: Intl.NumberFormat.prototype.formatToParts

2017-09-12 Thread Daniel Ehrenberg

Note that in 61, this feature was behind the
--js-flags=--harmony-number-format-to-parts command-line flag; it will
be added to about:flags (as part of the "experimental JavaScript
features" option) in an upcoming Canary, but is not presented that way
in the current Canary.

This is a V8 feature, so I'm not sure how to use OmahaProxy to verify
it directly. Here's how I verified that it was present in 61 behind
that command-line flag:

The current v8 version listed in OmahaProxy is 6.1.534.32 . If you
open a V8 checkout and do "git log 6.1.534", then contained in that
log is the commit with SHA-1 6c1e67f806d23ce23e398d3b21349d1be267
, Change-ID I306dd1721cc00c5820b061f14c4b6866f8d938f6 which implements
this feature.

Dan

On Tue, Sep 12, 2017 at 4:41 PM, 'Joe Medley' via blink-dev
 wrote:
> I'm looking for confirmation that's it's behind a flag in 61. I don't take
> the status entries word for it. I look for a commit hash I can look up in
> OmahaProxy.
>
> Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com |
> 816-678-7195
> If an API's not documented it doesn't exist.
>
> On Mon, Sep 11, 2017 at 2:32 PM, Adam Klein  wrote:
>>
>> I have the same question here as my latest question on the PluralRules
>> thread: any idea why Firefox isn't shipping this (yet), given they have it
>> implemented?
>>
>> On Sun, Sep 10, 2017 at 2:03 PM, Josh Wolfe  wrote:
>>>
>>> # Contact emails
>>>
>>> jwo...@igalia.com
>>> little...@chromium.org
>>>
>>> # Spec
>>>
>>> https://github.com/tc39/ecma402/pull/79
>>>
>>> # Summary
>>>
>>> Intl.NumberFormat.prototype.formatToParts() is scheduled to be added to
>>> the
>>> EcmaScript Internationalization API specification (Ecma 402). It adds a
>>> method
>>> to format a number to a list of tokens and their types (e.g. minusSign,
>>> integer,
>>> decimal, fraction, currency, percentSign, etc). It is implemented and
>>> disabled
>>> by default by Firefox. v8 implemented it behind a flag. See also, the
>>> corresponding DateTimeFormat feature here:
>>> https://www.chromestatus.com/feature/6319456309477376
>>>
>>> # Motivation
>>>
>>> A web form may want to display a price like "$1,234.00" with the
>>> fractional
>>> part ".00" in superscript and in a different color. If you use
>>> Intl.NumberFormat.prototype.format(), you get a string, which you would
>>> then
>>> need to parse to find the fractional part. However, the decimal separator
>>> is
>>> locale dependent, so attempting to account for this variability somewhat
>>> defeats the purpose of the locale-independent NumberFormat API. The
>>> solution is
>>> to expose the individual parts of the formatted string with tags to
>>> identify
>>> each part's role in the overall representation.
>>>
>>> # Interoperability risk
>>>
>>> * Firefox: In development
>>> * Edge: No public signals
>>> * Safari: No public signals
>>> * Web developers: No signals
>>>
>>> # Compatibility risk
>>>
>>> Low compatibility risk, as this feature is exposed through a new method
>>> `Intl.NumberFormat.prototype.formatToParts`.
>>>
>>> # Ongoing technical constraints
>>>
>>> None
>>>
>>> # Will this feature be supported on all six Blink platforms (Windows,
>>> Mac, Linux, Chrome OS, Android, and Android WebView)?
>>>
>>> Yes
>>>
>>> # OWP launch tracking bug
>>>
>>> https://bugs.chromium.org/p/v8/issues/detail?id=5244
>>>
>>> # Link to entry on the Chrome Platform Status
>>>
>>> https://www.chromestatus.com/feature/5686840812109824
>>>
>>>
>>> --
>>> --
>>> v8-users mailing list
>>> v8-users@googlegroups.com
>>> http://groups.google.com/group/v8-users
>>> --- You received this message because you are subscribed to the Google
>>> Groups "v8-users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to v8-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> 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 on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEvLGcKm8OBEE-zp%2BsyhvC%3DVwQHFKXS3KCLjC8HYRXc%3Drg%2Bc5Q%40mail.gmail.com.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJUhtG-M-V0JZ7iwq5-7C4sr01McSLzc3Kr4bxa%3DGCkYovB6Kg%40mail.gmail.com.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit

Re: [blink-dev] Re: [v8-users] Intent to Ship: Intl.PluralRules

2017-09-12 Thread Daniel Ehrenberg

I asked Zbigniew Braniecki about the status of
Intl.NumberFormat.prototype.formatToParts and PluralRules, and he told
me,

> Both are ready and need to be exposed. We've been waiting for them to reach 
> stage 4 to expose them to the Web
> NumberFormat.formatToParts is behind the flag - 
> http://searchfox.org/mozilla-central/source/js/src/builtin/Intl.cpp#1639
> and PluralRules is exposed on mozIntl (which is our chrome-only API for UI 
> internationalization that extends Intl API) - 
> http://searchfox.org/mozilla-central/source/toolkit/components/mozintl/mozIntl.js#73
> With you guys having land both I think we can expose them now. I'm happy to 
> work on the patch next week :)

In particular, Mozilla has been pushing these proposals for some time,
and has been held back by lack of buy-in from other browser vendors.

Dan

On Tue, Sep 12, 2017 at 9:45 AM,   wrote:
> This implementation is for SpiderMoneky shell only with addIntlExtras(Intl).
> It isn't available on Gecko yet.
>
> -- Makoto Kato
>
> 2017年9月12日火曜日 6時30分27秒 UTC+9 Adam Klein:
>>
>> Thanks, from the spec-stabilization side this sounds fine to me.
>>
>> Given that we'd be first to ship, I wonder if you have any more background
>> on the Firefox status: the intent lists it as "in development" there, but
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1270146 has been closed, and
>> says it's "Fixed in Firefox 53". But I'm running Firefox 55 locally and I
>> don't see it shipped there.
>>
>> On Sun, Sep 10, 2017 at 10:17 AM, Daniel Ehrenberg 
>> wrote:
>>>
>>> +blink-dev
>>>
>>> On Sun, Sep 10, 2017 at 7:16 PM, Daniel Ehrenberg
>>>  wrote:
>>> > ECMA 402 (Intl) tracks its proposals separately. You can see it listed
>>> > as Stage 3 at https://github.com/tc39/ecma402/ . There is a full
>>> > implementation in Firefox behind a flag. I'd say this spec is pretty
>>> > stable.
>>> >
>>> > Dan
>>> >
>>> > On Fri, Sep 8, 2017 at 7:39 PM, Adam Klein  wrote:
>>> >> What's the stability state of the spec? I don't see it on
>>> >> https://github.com/tc39/proposals
>>> >>
>>> >> On Fri, Sep 8, 2017 at 9:41 AM, Josh Wolfe  wrote:
>>> >>>
>>> >>> # Contact emails
>>> >>>
>>> >>> jwo...@igalia.com
>>> >>> litt...@chromium.org
>>>
>>> >>>
>>> >>> # Spec
>>> >>>
>>> >>> https://rawgit.com/caridy/intl-plural-rules-spec/master/index.html
>>> >>>
>>> >>> # Summary
>>> >>>
>>> >>> Intl.PluralRules is a new API which exposes language-dependent data
>>> >>> on
>>> >>> pluralization forms of numbers. Given a locale and a number,
>>> >>> Intl.PluralRules outputs a category, which can then be used for
>>> >>> selection of the pluralization form of surrounding text.
>>> >>>
>>> >>> # Motivation
>>> >>>
>>> >>> In English, 101st ends with "st" while 111th ends with "th". The
>>> >>> algorithm
>>> >>> for
>>> >>> determining the proper ordinal suffix is non-trivial and locale
>>> >>> specific.
>>> >>> A
>>> >>> proper international solution is implemented in ICU, and
>>> >>> Intl.PluralRules
>>> >>> exposes this solution to JavaScript developers.
>>> >>>
>>> >>> # Interoperability risk
>>> >>>
>>> >>> * Firefox: In development
>>> >>> * Edge: No public signals
>>> >>> * Safari: No public signals
>>> >>> * Web developers: Positive
>>> >>>
>>> >>> # Compatibility risk
>>> >>>
>>> >>> Low compatibility risk, as this feature is exposed through a new
>>> >>> field
>>> >>> `Intl.PluralRules`.
>>> >>>
>>> >>> # Ongoing technical constraints
>>> >>>
>>> >>> None
>>> >>>
>>> >>> # Will this feature be supported on all six Blink platforms (Windows,
>>> >>> Mac,
>>> >>> Linux, Chrome OS, Android, and Android WebView)?
>>> >>>
>>> >>> Yes
>>> >>>
>>> >>> # OWP launch tracking bug
>>> >>>
>>> >>> https://bugs.chromium.org/p/v8/issues/detail?id=5601
>>> >>>
>>> >>> # Link to entry on the Chrome Platform Status
>>> >>>
>>> >>> https://www.chromestatus.com/features/5653874773852160
>>> >>>
>>> >>> --
>>> >>> --
>>> >>> v8-users mailing list
>>> >>> v8-u...@googlegroups.com
>>> >>> http://groups.google.com/group/v8-users
>>> >>> --- You received this message because you are subscribed to the
>>> >>> Google
>>> >>> Groups "v8-users" group.
>>> >>> To unsubscribe from this group and stop receiving emails from it,
>>> >>> send an
>>> >>> email to v8-users+u...@googlegroups.com.
>>> >>> For more options, visit https://groups.google.com/d/optout.
>>> >>
>>> >>
>>> >> --
>>> >> --
>>> >> v8-users mailing list
>>> >> v8-u...@googlegroups.com
>>> >> http://groups.google.com/group/v8-users
>>> >> ---
>>> >> You received this message because you are subscribed to the Google
>>> >> Groups
>>> >> "v8-users" group.
>>> >> To unsubscribe from this group and stop receiving emails from it, send
>>> >> an
>>> >> email to v8-users+u...@googlegroups.com.
>>> >> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> You received this message because you are subscribed to the Google

Re: [v8-users] Intent to Ship: Intl.NumberFormat.prototype.formatToParts

2017-09-12 Thread Daniel Ehrenberg

I asked Zbigniew Braniecki about the status of
Intl.NumberFormat.prototype.formatToParts and PluralRules, and he told
me,

> Both are ready and need to be exposed. We've been waiting for them to reach 
> stage 4 to expose them to the Web
> NumberFormat.formatToParts is behind the flag - 
> http://searchfox.org/mozilla-central/source/js/src/builtin/Intl.cpp#1639
> and PluralRules is exposed on mozIntl (which is our chrome-only API for UI 
> internationalization that extends Intl API) - 
> http://searchfox.org/mozilla-central/source/toolkit/components/mozintl/mozIntl.js#73
> With you guys having land both I think we can expose them now. I'm happy to 
> work on the patch next week :)

In particular, Mozilla has been pushing these proposals for some time,
and has been held back by lack of buy-in from other browser vendors.

Dan

On Mon, Sep 11, 2017 at 11:32 PM, Adam Klein  wrote:
> I have the same question here as my latest question on the PluralRules
> thread: any idea why Firefox isn't shipping this (yet), given they have it
> implemented?
>
> On Sun, Sep 10, 2017 at 2:03 PM, Josh Wolfe  wrote:
>>
>> # Contact emails
>>
>> jwo...@igalia.com
>> little...@chromium.org
>>
>> # Spec
>>
>> https://github.com/tc39/ecma402/pull/79
>>
>> # Summary
>>
>> Intl.NumberFormat.prototype.formatToParts() is scheduled to be added to
>> the
>> EcmaScript Internationalization API specification (Ecma 402). It adds a
>> method
>> to format a number to a list of tokens and their types (e.g. minusSign,
>> integer,
>> decimal, fraction, currency, percentSign, etc). It is implemented and
>> disabled
>> by default by Firefox. v8 implemented it behind a flag. See also, the
>> corresponding DateTimeFormat feature here:
>> https://www.chromestatus.com/feature/6319456309477376
>>
>> # Motivation
>>
>> A web form may want to display a price like "$1,234.00" with the
>> fractional
>> part ".00" in superscript and in a different color. If you use
>> Intl.NumberFormat.prototype.format(), you get a string, which you would
>> then
>> need to parse to find the fractional part. However, the decimal separator
>> is
>> locale dependent, so attempting to account for this variability somewhat
>> defeats the purpose of the locale-independent NumberFormat API. The
>> solution is
>> to expose the individual parts of the formatted string with tags to
>> identify
>> each part's role in the overall representation.
>>
>> # Interoperability risk
>>
>> * Firefox: In development
>> * Edge: No public signals
>> * Safari: No public signals
>> * Web developers: No signals
>>
>> # Compatibility risk
>>
>> Low compatibility risk, as this feature is exposed through a new method
>> `Intl.NumberFormat.prototype.formatToParts`.
>>
>> # Ongoing technical constraints
>>
>> None
>>
>> # Will this feature be supported on all six Blink platforms (Windows, Mac,
>> Linux, Chrome OS, Android, and Android WebView)?
>>
>> Yes
>>
>> # OWP launch tracking bug
>>
>> https://bugs.chromium.org/p/v8/issues/detail?id=5244
>>
>> # Link to entry on the Chrome Platform Status
>>
>> https://www.chromestatus.com/feature/5686840812109824
>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> --- You received this message because you are subscribed to the Google
>> Groups "v8-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Re: [blink-dev] Intent to Ship: Async Iteration / Async Generators

2017-09-12 Thread Adam Klein

LGTM!

On Tue, Sep 12, 2017 at 9:48 AM, Caitlin Potter  wrote:

> *Contact Emails*
>
> ca...@chromium.org
>
> *Spec*
>
> https://tc39.github.io/proposal-async-iteration/
>
> *Summary*
>
> Async Generators and the new Async Iteration protocol provide tools for
> implementing and consuming data sources not synchronously available in
> their
> entirety. A common use-case is to wrap ReadableStreams for consumption via
> `for-await-of` loops (example: https://jakearchibald.com/2017/async-
> iterators-and-generators/).
>
> *Motivation*
>
> Promises and Streams are a part of the platform, both from the perspective
> of the world-wide-web,
> and from the perspective of Node.js. This feature provides a streamlined,
> readable interface for
> interacting with complex platform tools, and enables developers to more
> easily implement
> complex schemes which cannot run synchronously.
>
> *Interoperability risk*
>
> * Firefox: In development
> * Edge: Public support
> * Safari: In development
> * Web developers: No signals
>
> *Compatibility risk*
>
> Low compatibility risk. There is some risk due to Babel's shipment of an
> incorrect implementation of
> the standard, and the complexity of feature-testing. That said, the
> feature has been staged for several
> weeks now, and content creators most at risk of running into compatibility
> risks would have likely
> encountered them by now during this period.
>
> *Ongoing technical constraints*
>
> None (granted, more work is likely needed to reduce the overhead of the
> feature on low-end devices)
>
> *Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, Chrome OS, Android, and Android WebView)?*
>
> Yes
>
> *OWP launch tracking bug*
>
> 
> https://bugs.chromium.org/p/v8/issues/detail?id=5855
>
> *Link to entry on the Chrome Platform Status*
>
> https://www.chromestatus.com/feature/5727385018171392
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To view this discussion on the web visit https://groups.google.com/a/
> chromium.org/d/msgid/blink-dev/7DFC3057-2841-4B25-9568-
> FB896C162F20%40chromium.org
> 
> .
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Intent to Ship: Async Iteration / Async Generators

2017-09-12 Thread Caitlin Potter

Contact Emails

ca...@chromium.org 

Spec

https://tc39.github.io/proposal-async-iteration/ 


Summary

Async Generators and the new Async Iteration protocol provide tools for
implementing and consuming data sources not synchronously available in their
entirety. A common use-case is to wrap ReadableStreams for consumption via
`for-await-of` loops (example: 
https://jakearchibald.com/2017/async-iterators-and-generators/ 
).

Motivation

Promises and Streams are a part of the platform, both from the perspective of 
the world-wide-web,
and from the perspective of Node.js. This feature provides a streamlined, 
readable interface for
interacting with complex platform tools, and enables developers to more easily 
implement
complex schemes which cannot run synchronously.

Interoperability risk

* Firefox: In development
* Edge: Public support
* Safari: In development
* Web developers: No signals

Compatibility risk

Low compatibility risk. There is some risk due to Babel's shipment of an 
incorrect implementation of 
the standard, and the complexity of feature-testing. That said, the feature has 
been staged for several
weeks now, and content creators most at risk of running into compatibility 
risks would have likely
encountered them by now during this period.

Ongoing technical constraints

None (granted, more work is likely needed to reduce the overhead of the feature 
on low-end devices)

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

Yes

OWP launch tracking bug

 
https://bugs.chromium.org/p/v8/issues/detail?id=5
 855

Link to entry on the Chrome Platform Status

https://www.chromestatus.com/feature/5727385018171392 


-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [blink-dev] Re: [v8-users] Intent to Ship: Intl.PluralRules

Re: [blink-dev] Re: [v8-users] Intent to Ship: Intl.NumberFormat.prototype.formatToParts

Re: [blink-dev] Re: [v8-users] Intent to Ship: Intl.NumberFormat.prototype.formatToParts

Re: [blink-dev] Re: [v8-users] Intent to Ship: Intl.PluralRules

Re: [v8-users] Intent to Ship: Intl.NumberFormat.prototype.formatToParts

[v8-users] Re: [blink-dev] Intent to Ship: Async Iteration / Async Generators

[v8-users] Intent to Ship: Async Iteration / Async Generators

7 matches

Site Navigation

Mail list logo

Footer information