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 emailsmath...@chromium.org >>> <math...@chromium.org>Spechttps://github.com/tc39/proposal-json-superset >>> <https://github.com/tc39/proposal-json-superset>SummaryA Stage 3 proposal >>> makes ECMAScript a syntactic superset of JSON by allowing U+2028 and U+2029 >>> in string literals.MotivationECMAScript claims JSON as a subset in >>> JSON.parse <https://tc39.github.io/ecma262/#sec-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 riskFirefox: >>> Public supportEdge: Public supportSafari: Public supportWeb developers: >>> Strongly positiveCompatibility riskThis 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 >>> bughttps://bugs.chromium.org/p/v8/issues/detail?id=7418 >>> <https://bugs.chromium.org/p/v8/issues/detail?id=7418>Link to entry on the >>> Chrome Platform Status >>> dashboardhttps://www.chromestatus.com/features/6102319234023424 >>> <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/ch >>> romium.org/d/msgid/blink-dev/CAJYpFjDOzdTHBNJR0oheBPOtKCETJQ >>> UxPqd3pYCz3DA8%3DGKRTg%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJYpFjDOzdTHBNJR0oheBPOtKCETJQUxPqd3pYCz3DA8%3DGKRTg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> >> > -- -- 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.
