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

Update links to Cross-Origin Resource Sharing and Web Notifications #467

Closed
xfq opened this issue Jun 2, 2020 · 1 comment
Closed

Update links to Cross-Origin Resource Sharing and Web Notifications #467

xfq opened this issue Jun 2, 2020 · 1 comment
Labels

Comments

@xfq
Copy link
Member

xfq commented Jun 2, 2020

They are now W3C Superseded Recommendations:

@xfq xfq added the data label Jun 2, 2020
tidoust added a commit to tidoust/media-web-roadmap that referenced this issue Jun 5, 2020
This update updates the URL of WICG specs that have recently migrated to a
Working Group or whose repo name has changed:

- Migrations to the Web Applications Working Group: Badging API and Web Share
Target API
- Repo name changes: Web Background Synchronization and Input Device
Capabilities

Relevant text moved to "in progress" sections for migrations.

This update also makes CORS a feature of the Fetch spec and switches the
Notifications API to the WHATWG version (see w3c#467)

A few new implementation statuses seem to be reported by the Edge status
platform, this update also takes these new statuses into account.
xfq pushed a commit that referenced this issue Jun 5, 2020
This update updates the URL of WICG specs that have recently migrated to a
Working Group or whose repo name has changed:

- Migrations to the Web Applications Working Group: Badging API and Web Share
Target API
- Repo name changes: Web Background Synchronization and Input Device
Capabilities

Relevant text moved to "in progress" sections for migrations.

This update also makes CORS a feature of the Fetch spec and switches the
Notifications API to the WHATWG version (see #467)

A few new implementation statuses seem to be reported by the Edge status
platform, this update also takes these new statuses into account.
@xfq
Copy link
Member Author

xfq commented Jun 5, 2020

Fixed in #469

@xfq xfq closed this as completed Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant