w3c / w3c/editing

execCommand browser incompatibilities

Open
#289 2 comments 1 reaction 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

The spec aims to follow current browser implementations, with notes explaining incompatibilities, but some of this material is outdated. For example, it is no longer usual to flag issues with Internet Explorer, except perhaps to mention that IE's implementation is incompatible. A note to section 9.21 about different line-breaking behaviours in different browsers has been superseded: all current browsers converged on

more than five years ago. The note could be deleted.

In my opinion, the statement in the intro that browsers copied the APIs "in a haphazard and imprecise fashion" is unfair to current browser implementors because they appear to have largely converged since that was written. I suggest it be removed.

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

Read the specification's introduction and section 9.21, where the outdated browser-compatibility material is identified. Remove or update the statements described in the issue, then verify that the specification no longer presents obsolete Internet Explorer, line-breaking, or browser-implementation claims.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
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.