Closed Bug 41307 Opened 25 years ago Closed 25 years ago

nobr tag does not work

Categories

(Core :: Layout, defect, P2)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: conorlennon, Assigned: erik)

References

()

Details

(Keywords: platform-parity)

Attachments

(3 files)

From Bugzilla Helper: User-Agent: Mozilla/4.73 [en] (WinNT; U) BuildID: 2000060120 The nobr tag does not prevent line breaks. When the below html snippet is displayed, line breaks should only be inserted between the 'z' and 'A' and nowhere else. However, in Mozilla, line breaks are inserted ignoring the nobr and /nobr tags. Reproducible: Always Steps to Reproduce: 1. Set resolution to 1024x768 2. Go to http://members.xoom.com/_XMCM/conorl/Mozilla/nobr.html Actual Results: Line breaks are inserted where necessary, as if the nobr tag is being ignored. Expected Results: Line breaks should be inserted, where necessary, between 'z' and 'A' and nowhere else. html snippet: <html> <body> <nobr>A b c d e f g h i j k l m n o p q r s t u v w x y z</nobr> <nobr>A b c d e f g h i j k l m n o p q r s t u v w x y z</nobr> <nobr>A b c d e f g h i j k l m n o p q r s t u v w x y z</nobr> <nobr>A b c d e f g h i j k l m n o p q r s t u v w x y z</nobr> <nobr>A b c d e f g h i j k l m n o p q r s t u v w x y z</nobr> </body> </html>
Attached file Testcase for this bug.
Attached file Testcase for this bug.
This works fine for me in Linux mozilla 2000-06-01-08-M16.
I was not able to reproduce this bug on a PowerMac G3 running MacOS 8.6. Mozilla Build ID: 2000060208
Seeing this with 2000053108 on NT: doesn't manifest at some window sizes. When it does happen, the break generally appears toward the end of the NOBRed group (say, between w and x in the test-cases).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Not sure if this is of any use, but using the new testcase, I've produced the following data under Windows 95. I've inserted [Break here] where a line break occurs in the A b c..etc lines. -------------------------------------------------------------------------------- A b c d e f g h i j k l m n o p q r s t u v w x y z A b c d e f g h i j k l m n o p q r s t u v w x y z A b c d e f g h i j k l m n o p q r s t [Break here] u v w x y z A b c d e f g h i j k l m n o p q r s t u v w x y z A b c d e f g h i j k l m n o p q r s t u v w x y z [Break here] window.innerWidth=800 window.innerHeight=444 -------------------------------------------------------------------------------- A b c d e f g h i j k l m n o p q r s t u v w x y z A b c d e f g h i j k l m n o p q r s t u v w x y z [Break here] A b c d e f g h i j k l m n o p q r s t u v w x y z A b c d e f g h i j k l m n o p q r s t u v w x y z [Break here] A b c d e f g h i j k l m n o p q r s t u v w x y z [Break here] window.innerWidth=773 window.innerHeight=412 -------------------------------------------------------------------------------- A b c d e f g h i j k l m n o p q r s t u v w x y z A b c d e f g h i j k l m n o p q r s t u v w x y z A b c d e f g h i j k l m n o p q r [Break here] s t u v w x y z A b c d e f g h i j k l m n o p q r s t u v w x y z A b c d e f g h i j k l m n o p q r s t u v w x y z [Break here] window.innerWidth=777 window.innerHeight=423 -------------------------------------------------------------------------------- A b c d e f g h i j k l m n o p q r s t u v w x y z A b c d e f g h i j k l m n o p q r s t u v w x y z A b c d e f g h i j [Break here] k l m n o p q r s t u v w x y z A b c d e f g h i j k l m n o p q r s t u v w x y z [Break here] A b c d e f g h i j k l m n o p q r s t u v w x y z [Break here] window.innerWidth=688 window.innerHeight=348 -------------------------------------------------------------------------------- I could go on, but is there any point?
Reassiging to Kevin for bug triage.
Assignee: clayton → kmcclusk
The problem seems to be the line breaking code does not take into account the window width when determining when to break. I am seeing problems on WINNT as well. Reassigning to buster@netscape.com
Assignee: kmcclusk → buster
erik, can you do some initial analysis to see what is going wrong here? is it in the text code, or layout? because it is windows-only, I suspect troy's optomistic text measurement code, which runs on windows only
Assignee: buster → erik
Keywords: pp
Priority: P3 → P2
Confirmed that this bug occurs on Windows, but not on Linux. Marking M17 for now.
Status: NEW → ASSIGNED
Target Milestone: --- → M17
Works for me under Build 20000090308 on Windows NT.
Marking this bug as fixed, as it appears to be fixed to me. (tested in Build 2000090908)
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Marking verified per last comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: