Closed Bug 308206 Opened 19 years ago Closed 19 years ago

Mozilla ignores the ­ HTML code.

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 9101

People

(Reporter: Mark.Fenbers, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

There is no way to specify a line break hint in Firefox.  IE6 acts on both ­
and <wbr> (which is slightly different because &shy shows the hyphen, and <wbr>
does not).  Consequently, minimum column widths are wider in Firefox which cuts
off the right side of the table when printing whereas IE prints the whole table
nicely.  Support for <WBR> also existed in an earlier version of Netscape, but
Firefox never seemed to pick up this useful (and sometimes needed feature).  I
don't know why.  &shy; is part of the HTML standard:
http://www.w3.org/TR/html401/sgml/entities.html, but I haven't found if <wbr>
is.  It should be!  It's very useful is certain situations such as tightly
packed tables.

Reproducible: Always

Steps to Reproduce:
1.  Add &shy; characters to the HTML document near the end of the line and
observed that line breaks do not occur.
2.
3.

Actual Results:  
No line break occurs where it would otherwise.

Expected Results:  
... broken the word across line feed and put a small hyphen where the break occurs.
<wbr> is not a standard element in HTML.  Furthermore, there is already a bug
report dealing with this issue.  Resolving DULICATE.

*** This bug has been marked as a duplicate of 9101 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Summary: Mozilla ignores the &shy; HTML code. → Mozilla ignores the &shy; HTML code.
Mark, 
<wbr> is non-standard, but it works in firefox- *without* surrounding
<nobr></nobr> only.
Until bug 9101 is fixed (it's 6 jears old now and comes in scool...), 
you can use a cross-browser (but non-standard) workaround like this:

 xxxxxxxxxxxxxX&shy;<wbr>Xxxxxxxxxxxxxx

tschüs, jürgen
 
You need to log in before you can comment on or make changes to this bug.