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

TPAC planning and specification status report #111

Closed
LJWatson opened this issue Jun 19, 2020 · 1 comment
Closed

TPAC planning and specification status report #111

LJWatson opened this issue Jun 19, 2020 · 1 comment

Comments

@LJWatson
Copy link

LJWatson commented Jun 19, 2020

TPAC will be virtual this year. W3C is finalising the details but it is likely there will be events for the whole W3C community during the week of 26 to 31 October (as originally planned), with WG able to organise their own meetings in/around that week.

There are two things we need you to do:

  1. Let @marcoscaceres and I know before 17 July if you want meeting time to talk about your specification.
  2. Post a specification status report before 30 September.

The 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?

Your specification status report from 2019 is at #102

@johanneswilm
Copy link
Contributor

Some minor details are being clarified on level 1 as the Firefox is implementing. More extensive typing tests for level 1 have been added since last year. As far as I am aware, we are just waiting for the W3C to release a CR of level 1. Level 2 has not changed and has only been implemented by Webkit so far. Whether we will continue with some version of level 2 will likely be clarified once EditContext is being shipped.

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

3 participants