mdn / mdn/browser-compat-data

api.Document.execCommand - either mark as non-standard or add link to w3c draft

Open
#27,456 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

data:api
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the repository for the api.Document.execCommand entry and inspect how its standard status and spec_url metadata are represented. Compare the entry with the W3C execCommand draft and the linked MDN page, then make the metadata consistent and verify the resulting data format.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
api, documentation
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.