br vs wbr Break Opportunity Diff
Distinguishes a br line break from a wbr line-break opportunity. Both are void elements; actual line wrapping depends on layout.
Description
Br creates a line break; wbr creates an optional wrapping opportunity.
Br creates a line break; wbr creates an optional wrapping opportunity. They serve different authoring purposes even though both are void elements.1
Distinguishes a br line break from a wbr line-break opportunity. Both are void elements; actual line wrapping depends on layout.
When to use br vs wbr Break Opportunity Diff
Use this for the following task: Distinguishes a br line break from a wbr line-break opportunity. Both are void elements; actual line wrapping depends on layout.
Prepare the parsed attribute values, element states or ordered local lists requested below. Keep attribute presence separate from value.
How to use br vs wbr Break Opportunity Diff and understand its results
- Prepare the parsed attribute values, element states or ordered local lists requested below. Keep attribute presence separate from value.
- Enter tag using the field table, then run the tool.
- Read lineBreak, optionalBreakOpportunity. Interpret flags, units, ordering and placeholder values using the rules below.
- Review any reported issue or failed check, correct the supplied values when appropriate, and verify the result in its intended context.
| Input field | Meaning | Value type and bounds | Requirement |
|---|---|---|---|
| tag | Tag | string; choose "br", "wbr" | Required |
Choose the tag and return its break semantics.2
br → lineBreak; wbr → optionalBreakOpportunity This summarizes the declared operation. Units, indexing, inclusivity and exceptional cases are explained in the surrounding text.
| Output field | Meaning | Value type |
|---|---|---|
| lineBreak | Line Break | boolean |
| optionalBreakOpportunity | Optional Break Opportunity | boolean |
{
"input": {
"tag": "wbr"
},
"output": {
"lineBreak": false,
"optionalBreakOpportunity": true
}
}Limitations and assumptions
Actual wrapping depends on layout and CSS; no text measurement is performed.
This evaluates supplied local information; it does not fetch a page or run a browser. Malformed requests produce input errors. A successfully evaluated request can still contain false flags, empty result lists or a result outside the supplied threshold; those outcomes have the meanings stated above.
Alternative or Complementary methods
Choose b/i vs strong/em Semantic Split for this operation: Classifies b, i, strong and em by standard meaning: attention, alternate voice, importance or stress emphasis. Font weight and style are not inferred. For a complementary task, use Void Elements List Checker for this operation: Checks parsed HTML element names against the 13 current void elements; names are ASCII case insensitive. This does not parse markup or classify obsolete elements.
Further background: HTML / accessibility reference: br vs wbr Break Opportunity Diff.
References
Similar or alternative tools
- b/i vs strong/em Semantic Split
Classifies b, i, strong and em by standard meaning: attention, alternate voice, importance or stress emphasis. Font weight and style are not inferred.
- Void Elements List Checker
Checks parsed HTML element names against the 13 current void elements; names are ASCII case insensitive. This does not parse markup or classify obsolete elements.