- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Dec 2016 09:30:43 +0000
- To: public-css-archive@w3.org
kojiishi has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-text-3] Priority between break-all/break-word/hyphens == When these properties are set together, browses have different priorities. Test: http://output.jsbin.com/bivori Observations: | Browser | Priority | |-----|-----| | Edge | `break-all` > `hyphens` > `break-word` | | Gecko | `break-all` > `hyphens` > `break-word` | | WebKit | `hyphens` > `break-all`/`break-word` | | Blink | `break-all` > `break-word` > `hyphens` | >From a [user feedback](http://crbug.com/671341) and for consistency with other 3 browsers, I'm changing Blink to prioritize `hyphens` over `break-word`. This leaves a question whether `hyphens` should win over `break-all`, or opposite. Thoughts, anyone? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/791 using your GitHub account
Received on Tuesday, 6 December 2016 09:31:30 UTC