Request for a meeting on Storage Access API

[privacycg]

Request for a meeting on Storage Access API

[TanviHacks]

Would Thursday January 21st at 10am PST work? @johannhof @Brandr0id @johnwilander @jkarlin @jeremyroman @englehardt. That would be right after the PING call.

[johnwilander]

Confirmed that my conflicting meeting will be moved.

[johannhof]

@TanviHacks That would work for me, thank you.

[johnwilander]

I have a conflict 10:30-11:00 that I might be able to move.

[TanviHacks]

@johnwilander Let us know if you can move your 10:30. If so, we can confirm the time. Thank you!

[TanviHacks]

Okay then we are set for January 21st 10am PST. Using our regular call in details: https://github.com/privacycg/meetings/tree/master/2021/telcons. Please all mark your calendars.
Minutes

[johannhof]

Preliminary agenda from me, if you have time please take a look and feel free to suggest edits/additions:

(1) [40 mins] Work through interop Issues.

• privacycg/storage-access#25

  • Firefox is planning to align with Safari behavior, any concerns from Edge?

• privacycg/storage-access#36

  • Browsers seem to align on always rejecting without user gesture in cross-origin iframes, but differ in top-level context behavior (Safari resolves, Edge rejects).

• privacycg/storage-access#36

  • There's a new suggestion for a resolution from Firefox folks, would be great to get feedback on this.

• privacycg/storage-access#4

  • This probably needs a few words in the spec but might otherwise be punted to storage-partitioning.

• privacycg/storage-access#2

  • Firefox and Edge align on this as well as Safari Technology Preview, can we resolve this issue?

(2) [20 mins] Standardization.

• Are the spec editors (John and Tess) available to start resolving (inline) spec issues? What do they need help with?

• Can we identify issues that are blockers for standardization and assign someone to move them forward? Potential blockers:

  • inline spec issues

  • privacycg/storage-access#40

  • privacycg/storage-access#50

  • privacycg/storage-access#31

  • privacycg/storage-access#12 and privacycg/storage-access#10 (from Edge folks)

  • privacycg/storage-access#37

• Where do we want to move the spec as it matures?