word-break vs overflow-wrap Compare
Contrast supported line-break policies and min-content implications, not actual line layout or universal CJK behavior. Explicit supplied computed/layout context only; not a browser cascade/layout engine or cross-browser guarantee.
Description
Word-breaking policies affect where text may wrap and how intrinsic width is calculated.
Word-breaking policies affect where text may wrap and how intrinsic width is calculated.1
Emergency wrapping and broad word-breaking therefore need separate interpretation. Use word-break vs overflow-wrap Compare to look up a supported term.
When to use word-break vs overflow-wrap Compare
Use word-break vs overflow-wrap Compare to look up a supported term. Choose the exact supported token from the table; preserve its punctuation and capitalization.
How to use word-break vs overflow-wrap Compare and understand its results
- Choose the exact supported token from the table; preserve its punctuation and capitalization.
- Enter Wrap policy using the field table and validation rules below, then run the tool.
- Read Meaning and interpret units, signs, ordering and placeholders as explained below.
- If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| wrapPolicy | Wrap policy | string | Required; constraints below |
Enter one of the exact supported wrapPolicy tokens in the table below. The implementation performs a case-sensitive lookup and returns the stored meaning without interpreting a stylesheet, audio recording or performance. Unsupported tokens, added whitespace and alternate capitalization are input errors. The entries describe a bounded vocabulary rather than every valid value in the wider topic.
meaning = storedTable[exactSupportedToken] Field order, units and branch conditions follow the implementation explanation above.
| Exact supported token | Stored meaning |
|---|---|
| word-break:break-all | adds word-break opportunities broadly; does not retain ordinary whole-word overflow policy |
| overflow-wrap:anywhere | adds emergency opportunities that contribute to min-content size |
| overflow-wrap:break-word | adds emergency opportunities but they do not contribute to min-content size |
| word-break:normal | uses normal language-sensitive word breaking |
| Output field | Meaning | Value type |
|---|---|---|
| meaning | Stored explanation for the exact supported token. | string |
{
"input": {
"wrapPolicy": "overflow-wrap:anywhere"
},
"output": {
"meaning": "adds emergency opportunities that contribute to min-content size"
}
}Limitations and assumptions
Emergency wrapping and broad word-breaking therefore need separate interpretation. Apply the exact scope and assumptions described above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.
Alternative or Complementary methods
Use white-space Collapse Behavior Table for a related task: White-space handling controls collapsing, preserved breaks and wrapping.
Use text-orientation mixed/upright Lookup for a related task: Text orientation determines how characters are presented within vertical writing.
References
-
word-break vs overflow-wrap Compare — tool.io
Similar or alternative tools
- white-space Collapse Behavior Table
White-space handling controls collapsing, preserved breaks and wrapping.
- text-orientation mixed/upright Lookup
Text orientation determines how characters are presented within vertical writing.