mdn
api.Document.execCommand - either mark as non-standard or add link to w3c draft
What type of issue is this?
Missing specification link (no spec_url property)
What information was incorrect, unhelpful, or incomplete?
execCommand is currently marked as standard but has no spec_url. It has a draft thing at https://w3c.github.io/editing/docs/execCommand/, which is the best form of standardization we have (I think it's at least the same formalization as the Console spec).
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
We should either fully admit its non-standardization or add the spec_url, because it's currently inconsistent
Did you test this? If so, how?
/
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/Document/execCommand
MDN metadata
MDN page report details
- Query:
api.Document.execCommand - Report started: 2025-07-31T06:02:00.066Z
https://github.com/mdn/browser-compat-data/pull/24909 removed the spec_url, but didn't mark it as non-standard.
Meanwhile we have clarified in a BCD call that features without spec_url should always be marked as non-standard, and @Elchi3 is reviewing these cases in https://github.com/mdn/browser-compat-data/pull/27671 (because in some cases, we might just be missing the spec_url), and actually includes this change.
