Hey navigation-dev@,
A rough timeline of the Fenced Frames implementation over the past several months has looked like:
- A very rough Fenced Frames prototype to see how difficult it would be to get FF + MPArch working
- Design, implement, and test the short-/medium-term FF implementation based on ShadowDOM
- [In parallel to 2]: Get rendering and input working on top of Dom's (my) FF + MPArch initial prototype
At this point, wjmaclean@ was able to successfully get rendering and input working on the initial FF + MPArch prototype that I wrote a while back, and for various internal reasons we are currently prioritizing the MPArch path over the medium-term Origin Trial ShadowDOM approach.
In order to unblock the
MPArch tracker sheet for fenced frames, we need to land a concrete formal implementation of fenced frames, and it is the design for this that I've been working on for the past couple of weeks. This design is outlined in the "
Browser Process Design" section of my Fenced Frames implementation design doc, and I'd like to circulate it around to get more opinions and hopefully "approvals" on the overall approach.
So far I've asked altimin@, haraken@ to take an early look at the doc (thanks!) and I've been working on an implementation that is queued up in a few CLs. I'd love to get some input from someone on the CSA team (I've cc'd creis@ and alexmos@) before requesting formal reviews, so if there is any chance one of you could take a look that would be great! I'm happy to set up a meeting to go over any parts of the design that may not be clear as well.
Thanks,
Dom