Closed Bug 45367 Opened 25 years ago Closed 25 years ago

Regression in text legibility

Categories

(Core :: Layout, defect, P3)

defect

Tracking

()

VERIFIED DUPLICATE of bug 47154

People

(Reporter: pierre, Assigned: waterson)

References

()

Details

(Keywords: regression, top100)

Attachments

(1 file)

Verified with the latest (07/12) builds on Mac and Win98: - Go to the URL above. - Look at the text under the 2nd paragraph ("The Goal"). ==> Many spaces are missing between words, for instance: "conventionin", "toAmericans", "beenconvinced", "anunable", etc... The problem appears all over the article but it is particularly visible in the 2nd and the last paragraph. This regression appeared sometime between the 06/22 build and the 06/28 build.
I have been able to confirm this bug on several of the www.abcnews.go.com articles including their hacker kevin mitnick ones ;) http://abcnews.go.com/sections/tech/DailyNews/hacker000713.html It actually appears to be in the HTML code itself, FBI and on are joined, looking at the HTML source it appears as: The computer hacker who led the FBI on a three-year manhunt while allegedly causing millions of dollars so FBI and on are actually joined together. ie, FBIon Tho when I highlight and paste the text directly from the web page, it appears as: FBI on a three-year manhunt while allegedly causing millions of dol But displayed on webpage it looks like The computer hacker who led the FBIon a three-year manhunt while allegedly causing millions of
Oh yeah, I'm running 2000071221 on Linux 2.2.16 Slackware 7.1
Status: NEW → ASSIGNED
Keywords: nsbeta3, regression
Target Milestone: --- → M18
The HTML is correct. "FBI" and "on" are separated by a 0x0A. The problem is that some of these 0x0As result in a space and some don't. I haven't been able to find a logic in that. For instance in the first paragraph, we have "usenext" and "publicperception" without space while "Gore campaign" and "Daley said" do have a space. If you select "usenext", copy it and paste it into another application, you end up with "use nex", meaning that the content is correct; it's just the rendering that sometimes isn't.
ok, yeah, sounds about right, but for some reason when i view source it treats that 0x0A as a carriage return :)
Endorsing for nsbeta3 stopper as this is a correctness of rendering bug on top100 sites that renders text unreadable (unlessyoudon'tmindreadingEnglishwithoutspaces).
Keywords: correctness, top100
Whiteboard: (py8ieh:check if dup of suck.com bug)
CCd Ian. The two bugs that could be related to this one are bug 46631 and bug 47154.
Yup, it's a dup. Turns out the other problem is a lot more wide spread than I had originally believed. I have found dups in i18n bugs, in font bugs, in style bugs, in layout bugs... :-/ *** This bug has been marked as a duplicate of 47154 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Whiteboard: (py8ieh:check if dup of suck.com bug)
The bug this was duped against is now fixed, and I'm not seeing this behavior anymore. Verified dupe.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: