Invalid or identical colors provided to `backColor`/`foreColor`/`hiliteColor` should return `true` instead of `false`
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
If the value string provided to backColor, foreColor or hiliteColor is either an invalid CSS color or the current color, the spec states to return false:
As tested in both Firefox and Chrome, we should instead return true here.
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 at the linked execCommand specification section around lines 4201-4202 and review the stated behavior for backColor, foreColor, and hiliteColor. Done means the specification states that invalid or unchanged CSS colors return true, matching the behavior reported in Firefox and Chrome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100