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

[WebAPI] Implement getClientCapabilities #37516

Closed
8 tasks done
Tracked by #620
Rumyra opened this issue Jan 6, 2025 · 1 comment
Closed
8 tasks done
Tracked by #620

[WebAPI] Implement getClientCapabilities #37516

Rumyra opened this issue Jan 6, 2025 · 1 comment
Assignees

Comments

@Rumyra
Copy link
Collaborator

Rumyra commented Jan 6, 2025

Acceptance criteria

  • The listed features are documented sufficiently on MDN
  • BCD is updated
  • Interactive example and data repos are updated if appropriate
  • The content has been reviewed as needed

For folks helping with Firefox related documentation

  • Set bugs to dev-doc-complete
  • Add entry to Firefox release notes for enabled/preview features
  • Add/remove entry to Firefox experimental features page for preference/released features

Related Gecko bugs

https://bugzilla.mozilla.org/show_bug.cgi?id=1884466

Other

  • Check content open issues to see if any pertain to the subject matter. If there are any that can be closed because of the work, do so. If there are any that can be fixed relatively quickly because of the knowledge from completing this issue and you have time, feel free to go ahead and fix them.
@github-actions github-actions bot added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Jan 6, 2025
@Rumyra Rumyra added Content:WebAPI Web API docs Firefox 135 and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Jan 6, 2025
@Rumyra Rumyra mentioned this issue Jan 6, 2025
8 tasks
@hamishwillee hamishwillee self-assigned this Jan 20, 2025
@hamishwillee hamishwillee moved this from Todo to In Progress in MDN Web Docs Content Team Jan 20, 2025
@hamishwillee
Copy link
Collaborator

hamishwillee commented Jan 21, 2025

Status:

Note that the bits that haven't merged are IMO non-blocking. I'm closing because I'm unlikely to have to spend much more time on them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants