Use

 for IDL blocks · Issue #13 · w3c/pointerlock (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

A friendly request. In https://github.com/mdittmer/web-apis @mdittmer is working on tooling for extracting the IDL from specs linked to from Chromium's source code, for the purpose of comparing the IDLs. This will hopefully be a powerful tool for avoiding accidental differences.

In order to avoid having to use a real browser to scrape the IDL, it's useful if a <pre class=idl> block is used. This is one spec that Mark found relying on ReSpec's <dl class=pre> feature.

Note that this is already a ReSpec warning: "Defining WebIDL in dl elements is deprecated. Please use Contiguous IDL instead: https://github.com/w3c/respec/wiki/User's-Guide#webidl-support"