For future reference: this landed <https://chromium.googlesource.com/v8/v8.git/+/fd9251dbece8929a95cd16cabaa285ac5cb6d345%5E%21/> in V8 v6.6.257 and should thus be available in Chrome 66.
On Fri, Feb 16, 2018 at 7:58 PM, Benedikt Meurer <bmeu...@chromium.org> wrote: > LGTM! > > > On Fri, Feb 16, 2018 at 7:57 PM Sathya Gunasekaran <gsat...@chromium.org> > wrote: > >> LGTM >> >> On Fri, Feb 16, 2018 at 5:24 AM, PhistucK <phist...@gmail.com> wrote: >> > I know. >> > >> > Regarding "public support" - not "opposed" does not necessarily mean >> > "support" (it could be neutral). Transparency is important in >> > chromestatus.com (and in intent, I would argue). >> > Second, web developers are not part of the TC39 stages, so support or >> > reactions from them are not a given (not as far as "strongly positive"). >> > I think it makes sense to add links for opinions that are not your own. >> > >> > Just my two or three cents. >> > >> > >> > ☆PhistucK >> > >> > On Fri, Feb 16, 2018 at 3:07 PM, Mathias Bynens <m...@google.com> >> wrote: >> >> >> >> Note that since this is a V8/JS feature, this post is just an FYI to >> >> blink-dev — no signoff from Blink API owners is required. >> >> >> >> For ECMAScript features like this one, if a browser vendor would be >> >> opposed to this proposal, they would block its advancement at TC39. >> Given >> >> that this proposal already made it to Stage 3 I would be surprised if >> >> vendors would suddenly change their mind now. >> >> >> >> On Fri, Feb 16, 2018 at 1:50 PM, PhistucK <phist...@gmail.com> wrote: >> >>> >> >>> (At least on blink-dev) >> >>> "Interoperability risk" should have links for citing each vendor and >> web >> >>> developer support. >> >>> >> >>> >> >>> ☆PhistucK >> >>> >> >>> On Fri, Feb 16, 2018 at 2:15 PM, Mathias Bynens <math...@chromium.org >> > >> >>> wrote: >> >>>> >> >>>> Contact emails >> >>>> >> >>>> math...@chromium.org >> >>>> >> >>>> >> >>>> Spec >> >>>> >> >>>> https://github.com/tc39/proposal-json-superset >> >>>> >> >>>> >> >>>> Summary >> >>>> >> >>>> A Stage 3 proposal makes ECMAScript a syntactic superset of JSON by >> >>>> allowing U+2028 and U+2029 in string literals. >> >>>> >> >>>> >> >>>> Motivation >> >>>> >> >>>> ECMAScript claims JSON as a subset in JSON.parse, but (as has been >> >>>> well-documented) that is not true because JSON strings can contain >> unescaped >> >>>> U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR characters while >> >>>> ECMAScript strings cannot. >> >>>> >> >>>> These exceptions add unnecessary complexity to the specification and >> >>>> increase the cognitive burden on both implementers and users, >> allowing for >> >>>> the introduction of subtle bugs. Also, as a lesser but concrete >> corollary >> >>>> problem, certain source concatenation and construction tasks >> currently >> >>>> require additional steps to process valid JSON into valid ECMAScript >> before >> >>>> embedding it. >> >>>> >> >>>> >> >>>> Interoperability risk >> >>>> >> >>>> Firefox: Public support >> >>>> >> >>>> Edge: Public support >> >>>> >> >>>> Safari: Public support >> >>>> >> >>>> Web developers: Strongly positive >> >>>> >> >>>> >> >>>> Compatibility risk >> >>>> >> >>>> This change is backwards-compatible. User-visible effects will be >> >>>> limited to the elimination of SyntaxError completions when parsing >> strings >> >>>> that include unescaped LINE SEPARATOR or PARAGRAPH SEPARATOR >> characters, >> >>>> which in practice are uncommon. >> >>>> >> >>>> >> >>>> Is this feature fully tested? >> >>>> >> >>>> Yes; see >> >>>> v8/test/cctest/test-parsing/LineOrParagraphSeparator{ >> AsLineTerminator,InStringLiteral,InStringLiteralHarmony}. >> >>>> >> >>>> >> >>>> Tracking bug >> >>>> >> >>>> https://bugs.chromium.org/p/v8/issues/detail?id=7418 >> >>>> >> >>>> >> >>>> Link to entry on the Chrome Platform Status dashboard >> >>>> >> >>>> https://www.chromestatus.com/features/6102319234023424 >> >>>> >> >>>> >> >>>> Requesting approval to ship? >> >>>> >> >>>> Yes >> >>>> >> >>>> -- >> >>>> 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/ >> CAJYpFjDOzdTHBNJR0oheBPOtKCETJQUxPqd3pYCz3DA8%3DGKRTg%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. >> >> -- >> -- >> 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. >> > -- > > > > * • * > *Benedikt Meurer** • **Google Germany GmbH* > * • *Erika-Mann-Str. 33 > <https://maps.google.com/?q=Erika-Mann-Str.+33*+**%C2%A0%E2%80%A2+%C2%A0*80636+Munich&entry=gmail&source=g> > * • > <https://maps.google.com/?q=Erika-Mann-Str.+33*+**%C2%A0%E2%80%A2+%C2%A0*80636+Munich+%3Chttps://maps.google.com/?q%3DErika-Mann-Str.%2B33*%2B**%25C2%25A0%25E2%2580%25A2%2B%25C2%25A0*80636%2BMunich%26entry%3Dgmail%26source%3Dg%3E&entry=gmail&source=g>*80636 > Munich > <https://maps.google.com/?q=Erika-Mann-Str.+33*+**%C2%A0%E2%80%A2+%C2%A0*80636+Munich&entry=gmail&source=g> > > • bmeu...@google.com > > > Geschäftsführer: Paul Manicle, Halimah DeLaine Prado > > Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: > Hamburg > > Diese E-Mail ist vertraulich. Wenn Sie nicht der richtige Adressat sind, > leiten Sie diese bitte nicht weiter, informieren Sie den Absender und > löschen Sie die E-Mail und alle Anhänge. Vielen Dank. This e-mail is > confidential. If you are not the right addressee please do not forward it, > please inform the sender, and please erase this e-mail including any > attachments. Thanks. > -- -- 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.
