Should contenteditable have break-word behavior by default?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Filing to track the debate in this blink bug. Blink sets break-word and -webkit-line-break by default on contenteditable containers, and some sites (like fixya.com) appear to depend on this.
In particular Koji asks:
I would like the interoperability issue discussed, have a consensus in the group, and specified in the content editable spec the group is working on.
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 discussion in issue #145 and the linked Blink bug 427135, focusing on Blink's default behavior for contenteditable containers. Review the interoperability concerns and the content editable specification discussion; done means the group reaches consensus and the behavior is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100