-
Notifications
You must be signed in to change notification settings - Fork 16
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 2022 status report #111
Comments
Also, potential topics:
|
Sorry I'm not sure what (if anything) is being asked of me here. |
@inexorabletash, sorry for the oversight! Thanks for adding topics and will be sure to put it on the agenda. |
Sorry @aboodman - no action needed from you. I saw your Twitter thread and wanted to ACK it and discuss getting browser behaviors documented/standardized. |
2022 Status ReportProgress in the last 12 months
Normative changes:
Editorial changes:
Implementer updates:
Active PRs: Expected near future work:
Moving to CR/Rec
@saschanaz - did I miss anything? Will you be attending TPAC (virtually or physically) and anything you want to schedule time to discuss? |
I think I have nothing specific to talk about. I won't be physically at TPAC but maybe virtually. |
Web Locks is not part of the W3C /TR documents yet. Look forward to publishing it as a First Public Working Draft. Please let us know when the spec is ready :) |
@saschanaz, @inexorabletash, all good for us to send a publication request for FPWD? (i.e., any blockers?) If all good, I can prepare the CFC and send it to the WG. |
No blockers I'm aware of. |
Fixing #75 first would be ideal, but that's not blocking IMO. |
Thanks @inexorabletash and @saschanaz. @siusin, filed #112 and send email to public-webapps. Closing. |
Hey @LJWatson @marcoscaceres @siusin
This spec wasn't included in w3c/webappswg#87 but per #84 (comment) this is part of the WG charter. Do y'all want a status report?
cc: @saschanaz
The text was updated successfully, but these errors were encountered: