w3c / w3c/editing

Recursively executing `execCommand()` should be prevented

Open
#477 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

execCommand
Dominant language
HTML
Stars
202
Forks
43
PR merge metrics
No merged PRs in 30d

Description

All major browsers refuse to execute execCommand() recursively and return false, e.g. when calling it inside an input event handler as a result of another execCommand(). This is missing from the current spec.

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

The issue names execCommand() and input event handlers but no repository file or test. Start by locating the execCommand() specification and its recursion behavior; done means recursive calls are prevented and return false, matching the stated browser behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.