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.

Sign up for GitHub

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

Jump to bottom

Spec should not specify behavior of other specs in Editors Draft status (i.e., Reporting API) #241

Open
w3cbot opened this issue Aug 6, 2021 · 5 comments
Open

Spec should not specify behavior of other specs in Editors Draft status (i.e., Reporting API) #241

w3cbot opened this issue Aug 6, 2021 · 5 comments
Assignees
@samuelweiler
Labels
close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. s:html https://html.spec.whatwg.org/multipage/ whatwg https://whatwg.org/

Comments

@w3cbot
Copy link

w3cbot commented Aug 6, 2021

This is a tracker issue. Only discuss things here if they are privacy group internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ whatwg/html#6933
@w3cbot w3cbot added needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:html https://html.spec.whatwg.org/multipage/ close? The related issue was closed by the Working Group labels Aug 6, 2021
@samuelweiler
Copy link
Contributor

I'm taking point on this issue.

@samuelweiler samuelweiler self-assigned this Aug 17, 2021
@samuelweiler samuelweiler removed the pending Issue created by the tracker tool and may need to be refined label Aug 30, 2021
@samuelweiler
Copy link
Contributor

Having been told "no" by WHATWG, referring this to the W3C HTML WG for resolution:

https://lists.w3.org/Archives/Public/public-html/2021Aug/0006.html
https://lists.w3.org/Archives/Public/public-html/2021Aug/0005.html
w3c/htmlwg#20

@samuelweiler
Copy link
Contributor

reviewed as part of routine triage. No change. Keep it open.

@samuelweiler
Copy link
Contributor

samuelweiler commented Jan 31, 2022 •
edited
Loading

Update: the W3C HTML WG issued a call for consensus to publish the HTML spec as a candidate recommendation with a non-normative statement re: the reporting API hooks, as we had requested.

One of the WHATWG editors objected, saying the WHATWG/W3C MoU doesn't allow that. In further discussion, he suggested escalating the issue to the WHATWG steering group (SG).

Ultimately, the CfC closed with no support(!) and two objections. The ball is in the hands of the HTML WG, and one chair says "The next step will be to consider both objections with a view to finding a positive resolution in both cases."

w3c/htmlwg#22

@samuelweiler
Copy link
Contributor

Update: the HTML WG chairs have asked us to work to resolve the triggering issue on the Reporting API but, as yet, have not answered my clarifying questions.

With apologies, this discussion is in member-only space:
https://lists.w3.org/Archives/Member/w3c-archive/2022Mar/0605.html
https://lists.w3.org/Archives/Member/w3c-archive/2022Mar/0607.html

@w3cbot w3cbot added the whatwg https://whatwg.org/ label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@samuelweiler samuelweiler

Labels
close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. s:html https://html.spec.whatwg.org/multipage/ whatwg https://whatwg.org/
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@w3cbot @samuelweiler