Look if we need to add a fallback for `word-break`
See original GitHub issueCurrently we are using word-break: break-word;
in various places like code
.
This isn’t a standard property, at least not yet.
See if we need to provide a fallback.
/CC @mdo @MartijnCuppens
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
word-wrap break-word does not work in this example
Word-Break has nothing to do with inline-block . Make sure you specify width and notice if there are any overriding attributes in parent...
Read more >word-break - CSS: Cascading Style Sheets - MDN Web Docs
The word-break CSS property sets whether line breaks appear wherever the text would otherwise overflow its content box.
Read more >hyphens | CSS-Tricks
The hyphens property controls hyphenation of text in block level elements. You can prevent hyphenation from happening at all, allow it, ...
Read more >wrap, overflow - wrap - , and - word - break - LogRocket Blog
This property specifies whether the browser may break at otherwise disallowed points within a line to prevent overflow when an otherwise- ...
Read more >[css-text-3] Implement or unship word-break:break-word #2390
We resolved to add word-break:break-word if Firefox and Edge found it necessary to implement for web compat reasons. It's been two years, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We don’t, thus how I actually noticed the issue. Using vnu.jar’s web interface, which can also lint CSS, I saw the
break-word
errors and then looked into it.IMO we shouldn’t use non-standard properties when possible, and when we do we need to make sure we have fallbacks.
Because something works in Chrome/Chromium, certainly doesn’t mean is standard, and we shouldn’t endorse this.
/CC @twbs/css-review