One year update: fenced frames with local unpartitioned data access

[shivanigithub]

Session description

This breakout session will serve as a 1 year update to the "fenced frames with local unpartitioned data access" project. We will:

• Briefly recap the fenced frames with local unpartitioned data access explainer.

• Go over implementation progress in Chrome and highlight solutions that may be valuable to other developers.

Notes: https://pad.w3.org/p/FencedFramesBreakoutNotes
Slides:
Presentation: https://docs.google.com/presentation/d/1xKwCrhN2pD_lxuPfurgjEDkfyAcf3wgxPS9njlG9tT0/edit?usp=sharing
PDF: https://drive.google.com/file/d/1atW2LNCthu08-glzBXxcdY3dkoSC5ahv/view?usp=sharing

Session goal

To present implementation and design updates, and welcome feedback on any use cases that may benefit from this.

Additional session chairs (Optional)

@VergeA, @jkarlin, @zcancio

Who can attend

Anyone may attend (Default)

IRC channel (Optional)

#fenced-frames

Other sessions where we should avoid scheduling conflicts (Optional)

#32, #79

Instructions for meeting planners (Optional)

No response

Agenda for the meeting.

No response

Links to calendar

• 2024-09-25, 08:30 - 09:30

Meeting materials

• Slides
• Minutes

[tpac-breakout-bot]

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

[zcancio]

If possible, can this not conflict with #32