On Tue, Aug 22, 2023 at 5:02 PM Dominic Farolino <[email protected]> wrote:
> It looks like the spec PR here has been dormant for something like ~9 >> months. Are there any plans to help drive it to the finish line, >> especially given the TODOs listed in the OP? How should we all think about >> whatever work might remain there, and possibly deviate from what Chrome >> plans on shipping? >> > > Hello, I'm still a little curious if there are plans to advance the spec > PR anymore, so that it matches what we're attempting to ship? Or is there > something new that has superseded that work, making it (and my question) > obsolete? > The spec PR is still the latest. We had settled on a gradual CORB -> ORB transition, where this is the 2nd step. We initially had quite a few carveouts due to compat concerns, and we're working through them with this series of changes. I still hope that in the end we'll have a pretty good approximation of ORB and won't actually have many change requests to the current proposal. The thing is that right now, I wouldn't know what to ask for. So my plan is to keep implementing the proposed spec until I hit roadblocks, and then go back to the proposal. One new thing that may change this dynamic a bit is that FF is also working on it (see Olli's post). But the info I've got so far is that their carve-outs are similar to ours, except they've implemented the JS/JSON-distinguisher step. Which I'd like to be our next step, "v0.3". The end goal is certainly that the two implementations & the spec should match exactly. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALG6KPNVCdsRpi4KP1CXkK-R75YrCU%2Bxb2NP%2BoYSzizU7spwew%40mail.gmail.com.
