Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status report and planning for TPAC 2021 #479

Closed
LJWatson opened this issue Aug 25, 2021 · 4 comments
Closed

Status report and planning for TPAC 2021 #479

LJWatson opened this issue Aug 25, 2021 · 4 comments

Comments

@LJWatson
Copy link

TPAC will be virtual again this year. There will be a WebApps WG meeting at some point between 24 and 29 October.

There are two things we need you to do in the meantime:

  1. Let @marcoscaceres and I know before 17 September if you plan to hold a specification specific meeting (in addition to the general WebApps WG meeting)
  2. Post a specification status report before 30 September

Your specification status report should include:

  • What progress has your spec made in the last 12 months?
  • Is anything blocking your spec from moving to CR?
  • If yes, what is your plan to unblock it and do you need any help?

CC @siusin

@marcoscaceres
Copy link
Member

Reminder that the WG is meeting on Tuesday 26 October 2021, 9PM to 11PM UTC.

It would great if someone could give an 5 minute update on the state of this spec.

@szager-chromium
Copy link
Collaborator

szager-chromium commented Oct 26, 2021

These are the issues I would like to nail down for CR:

issue #95 : visual vs. layout viewport -- tentatively decided in favor of visual; objections?
issue #386 : how to define content clip -- not currently a compat issue, just need to find the right spec language
issue #432 : clarify isIntersecting when thresholds does not contain zero -- a hair-splitting but important issue, waiting for feedback...

Also for discussion: V2 has been shipped in chromium for ~2 years, and usage is ~4.5% of page loads. Apple has expressed willingness to accept WebKit patches to implement this. There is no formal spec position from Mozilla; prior discussions involved dbaron, who has since switched teams. Update from Mozilla?

@zcorpan
Copy link
Member

zcorpan commented Oct 26, 2021

I'd like to discuss #431 if there's time.

@marcoscaceres
Copy link
Member

Closing as done...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants