respec w3c common migration guide - speced/respec GitHub Wiki

The respec-w3c-common ReSpec profile has been deprecated and will not receive any updates in future, including the support for W3C 2020 Process.

What do I need to do?

In most specs, you can migrate to the respec-w3c profile by simply replacing:

<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove" defer></script>

with:

<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove" defer></script>

If you face issues with above, please file an issue or get in touch the W3C Slack's #respec channel, or via the spec-prod mailing list.

Why upgrade?

The respec-w3c profile contains security, performance, and new features plus support for the W3C's 2020 Process and future W3C Process/template updates. As such, it's highly recommended that you do upgrade.

  • #2838 explains the rationale behind deprecation.
  • #2889 shows the deprecation status and upcoming changes.

If you still don't wish to upgrade, please download a desired version of respec-w3c-common from npm or GitHub repository and self-host it.

💖 Support ReSpec by becoming a sponsor via Open Collective. 💖

✨ View rendered version of this documentation at https://respec.org/docs/ ✨

⚠️ **GitHub.com Fallback** ⚠️