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

Update review of monitored specs #286

Merged
merged 2 commits into from
May 3, 2021
Merged

Update review of monitored specs #286

merged 2 commits into from
May 3, 2021

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented May 1, 2021 •
edited by tidoust
Loading

The following specs have been updated since the last review:

@sideshowbarker
Copy link
Contributor

To the degree that existence of documentation in MDN is a relevant data point:

  • wicg.github.io/sanitizer-api updated on 2021-04-30T12:03:42.000Z; last comment: “Early proposal, no clear implementation plans” made on 2021-03-01

Sanitizer is documented in MDN at https://developer.mozilla.org/docs/Web/API/Sanitizer — along with its constructor and methods.

  • drafts.csswg.org/css-fonts-5 updated on 2021-04-06T16:25:36.000Z; last comment: “Marked as not ready for implementation” made on 2021-03-01

The CSS Fonts 5 size-adjust feature is documented in MDN at https://developer.mozilla.org/docs/Web/CSS/@font-face/size-adjust

Otherwise, as far MDN goes, none of the other documents listed in the issue description have documentation yet in MDN.

@sideshowbarker
Copy link
Contributor

I notice https://wicg.github.io/virtual-scroller/ says “This project is no longer being actively developed.”

So should that one be moved to ignore.json?

@sideshowbarker
Copy link
Contributor

So per #286 (comment) since https://wicg.github.io/sanitizer-api/ and https://drafts.csswg.org/css-fonts-5/ both have features documented in MDN, should we move them to spec.json? If so, do that by adding a commit to this PR branch, or do I instead up a new PR for each?

@dontcallmedom
Copy link
Member

dontcallmedom commented May 3, 2021 •
edited by sideshowbarker
Loading

either adding to this pull request or creating a new ones would be OK.

It's clear that sanitizer should be added since it has implementation take up in FF (based on BCD); I'm less clear on css-fonts-5 since:

  • size-adjust doesn't have a BCD entry

https://github.com/mdn/browser-compat-data/blob/main/css/at-rules/font-face.json#L610 in the sources has it, right? But it was added 11 days ago, so maybe it didn’t make it into a BCD release yet.

  • as @tidoust noted, the spec is marked as "not ready for implementation"

Do you know if it's being implemented anywhere yet?

Per that BCD entry, it’s implemented in Firefox 89+ under a flag.

@tidoust
Copy link
Member

tidoust commented May 3, 2021

Note that I'm preparing an update to this PR.

@tidoust tidoust marked this pull request as ready for review May 3, 2021 08:15
@tidoust
Copy link
Member

tidoust commented May 3, 2021

I updated the PR with the following changes:

Moved to ignore list:

  • Virtual scroller - no longer being considered as reported by @sideshowbarker

Moved to browser-specs list:

  • Open Screen Protocol - published as FPWD
  • Sanitizer API - behind a flag in Firefox, in development in Chrome
  • Scheduling APIs - spec filled out and origin trial in Chrome

Comment updated:

  • Raw Sockets API - no clear implementation plan, harmful for Mozilla
  • Conversion Measurement API - spec filled out but no clear implementation plan
  • Manifest Incubations - spec filled out but Chromium specific
  • App History - spec filled out but still early exploration

I did not update css-fonts-5 for now. Ideally, we'd have the CSS WG remove the banner if the properties are actually implemented in browsers.

@tidoust
Refresh monitor list
51aaa7d 
Moved to ignore list:
- Virtual scroller - no longer being considered

Moved to browser-specs list:
- Open Screen Protocol - published as FPWD
- Sanitizer API - behind a flag in Firefox, in development in Chrome
- Scheduling APIs - spec filled out and origin trial in Chrome

Comment updated:
- Raw Sockets API - no clear implementation plan, harmful for Mozilla
- Conversion Measurement API - spec filled out but no clear implementation plan
- Manifest Incubations - spec filled out but Chromium specific
- App History - spec filled out but still early exploration
@tidoust tidoust force-pushed the monitor-update-1619836485 branch from 9cf362d to 51aaa7d Compare May 3, 2021 08:26
@tidoust
Copy link
Member

tidoust commented May 3, 2021

I did not update css-fonts-5 for now. Ideally, we'd have the CSS WG remove the banner if the properties are actually implemented in browsers.

Discussion moved to the main missing specs for BCD issue: #279 (comment)

@tidoust tidoust merged commit 30a11d0 into master May 3, 2021
@tidoust tidoust deleted the monitor-update-1619836485 branch July 1, 2021 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dontcallmedom dontcallmedom dontcallmedom approved these changes

Assignees

@sideshowbarker sideshowbarker

@dontcallmedom dontcallmedom

@tidoust tidoust

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@sideshowbarker @dontcallmedom @tidoust