Interop 2022 and `execCommand`
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
From https://github.com/web-platform-tests/interop-2022/issues/17, it seems like a large chunk of editing-related WPT reveal inconsistent cross-browser behavior due to different execCommand behaviors.
execCommand is deprecated, but is still used widely on the web. Furthermore, execCommand behavior (and editing in general) behaves differently across different browsers, and even different platforms. How should we proceed with execCommand-related WPT failures?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Interop 2022 issue and review the execCommand-related Web Platform Tests failures it identifies. Done would require an agreed direction for handling these cross-browser and cross-platform inconsistencies, but the issue does not name specific test files or a concrete change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- testing, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100