312328 - <td> text without whitespace bleeds into adjacent column

Status: RESOLVED WORKSFORME

(Core :: Layout: Tables, defect)

Description

[James K. Lowden]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

See the comment in the URL I cite that starts "This guy says that ISP's that
allow spammers need to be pressured into stopping the spammers."  It is rendered 

|This guy says that ISP's that allow s|pammers need 
|to be pressured into stopping the spa|mmers.
                                       ^^^^ next column over
should be:

|This guy says that ISP's that allow  |
|spammers need to be pressured into   |
|stopping the spammers.               |

The rest of the text has the same problem, and other comments (cf. PREV/NEXT
links) don't have the same problem.  

I think the culprit is the URL text
(http://freesoftwaremagazine.com/free_issues/is sue_06/neednt_eat_spam/) at the
beginning of the <td>.  Because it has no whitespace, gecko (?) decides
incorrectly how many characters wide the column is.  

According to Page Info, the page is encoded ISO-8859-1, viewed at normal zoom
with Window's default fonts.  



Reproducible: Always

Steps to Reproduce:
1. Enter cited URL in the address bar.
2. View page. 


Actual Results:  
See details.  

Expected Results:  
It should color inside the lines, of course. ;-)
Other comments pages render correctly (e.g.
http://linuxtoday.com/news_story.php3?ltsn=2005-10-13-001-26-OS-NT-0005); it's
just this one that has a problem.

Comment 1

[Casey Weston]

http://freesoftwaremagazine.com/free_issues/issue_06/neednt_eat_spam/

Above should be the proper URL. There are no comments listed at that exact URL,
I clicked the link leading to the comments for that article and I found no text
matching the text you cite.

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915
Firefox/1.0.7

Comment 2

[James K. Lowden]

The comments I'm referring to are in the URL mentioned just above the summary of
this bug report:
http://linuxtoday.com/news_story.php3?ltsn=2005-10-13-001-26-OS-NT-0004

Sorry that wasn't clear. 

Interesting to note: now that I'm home running Firefox 1.02 on NetBSD, I see the
same page renders fine.  It would appear that the problem is perhaps either in
more recent versions or is Windows-specific in some way.  

Comment 3

[Boris Zbarsky [:bzbarsky]]

Is this still an issue on the URI in the url field in a current trunk build?

Comment 4

[Boris Zbarsky [:bzbarsky]]

No patch, so it wasn't fixed...

Comment 5

[James K. Lowden]

The link I had a problem with is in the "URL" field of this bug report.  It's still a viable page, so anyone can view it and confirm/deny my results.  

I don't have a trunk build handy.  I tested it with 1.5.0.3 on Win32.  It works fine.  So, either it's fixed or I can't reproduce the problem I reported (now using the current release).  That's certainly progress, because with 1.07 it could be reproduced at will.  

IMHO this bug should be closed FIXED unless and until someone finds a modern version of Fox that can't properly display the page.  

Comment 6

[Boris Zbarsky [:bzbarsky]]

The point is, the FIXED resolution is used when we know exactly what code changes fixed the bug.  If the issue disappeared but no one knows why, the WORKSFORME resolution is used.