264913 - Slashdot story pages do not render properly most of the time

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[A S]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

I know this bug is here somewhere, but I can't find it.  Why is it that Slashdot
is continually misrendered in Firefox? It happens on nearly every computer using
FF, but never in IE or Opera.  Never in KHTML/Konq that I've seen.  Never in
Epiphony that I've seen.  It's so common now, I've pretty much taken to not
using FF for Slashdot, which is PAINFUL.  You've gotta know that many ff users
visit Slashdot - this would be a HUGE win to fix this! 

*from spreadfirefox user 13489*

Reproducible: Sometimes
Steps to Reproduce:
1. visit slashdot.org
2. click "read more" on any story

Actual Results:  
misrendered over and over.  refreshing rarely helps.  

Expected Results:  
rendered the page properly.

Comment 1

[Bill Mason]

*** This bug has been marked as a duplicate of 217527 ***

Comment 2

[A S]

This is not a dupe of bug 217527.  As seen in this screenshot
(https://bugzilla.mozilla.org/attachment.cgi?id=154064&action=view) which isn't
mine, this is not the rendering problem with the left column overlapping on the
index page, this is the story being COMPLETELY off the page (the comment box on
the "post" pages).  I'm using PR .10 and the column bug is gone, but the story
bug is not.  

I'm reopening this bug - I hope that's ok, I don't know if that's the right
procedure - but it should probably be acknowledged if it is the same bug or
another Slashdot rendering bug.  

Comment 3

[Martijn Wargers (dead)]

Reporter, could you try a most recent nightly (1.8a) build?
http://ftp.scarlet.be/pub/mozilla.org/firefox/nightly/latest-trunk/
There are a lot of changes between 1.7 and 1.8a, so this could already been
fixed since then.

Comment 4

[Jonathan Wilson]

Attachment: screenshot

screenshot of what I assume is the problem..
This is from mozilla 1.7.2 so its not specific to FF.

Comment 5

[Martijn Wargers (dead)]

But is the bug reproducable in a recent nightly build?

Comment 6

[A S]

(In reply to comment #3)
> Reporter, could you try a most recent nightly (1.8a) build?

I downloaded the newest nightly build (18 Oct) of Moz Suite 1.8, then downloaded
the ff nightly from the link you sent. I can't be positive, but I can tell you
that I have not yet been able to reproduce the rendering bug.  Typically, it can
be reproduced at least one out of every three times or so, but I haven't yet
seen the problem again since the upgrade on any "story" page or comment page. 

For the record: 
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041018
Firefox/0.10.1

Comment 7

[Evan Hamrick]

Happens to me as well, fairly regularly. Fx 10-06 build and many many many
earlier builds.  Think it was fixed at some point in the trunk but some other
major bug caused me to go back to  branch...

Comment 8

[Martijn Wargers (dead)]

Marking WORKSFORME. This bug is probably fixed at some time in the 1.8a
development cycle.
If this bug is seen in the latest nightly trunk (1.8a) build, then it can be
reopened.

Comment 9

[A S]

Attachment: misrendering of Slashdot.org website

screenshot of Slashdot problem, which appeared to be fixed in several nightly
builds throughout October, but is somehow present again in 1.0 RC1 en-US.

Comment 10

[A S]

This bug appeared to be fixed in many of the nightlies I tried over the second
half of October.  Since downloading and installed 1.0 RC1 this morning, I've
experienced this problem no fewer than 5 times, as compared to ZERO since 10-19,
when I started using a nightly build.  

Unfortunately, this problem is not yet fixed.  I'll attach more screenshots of
the same bug. 

Comment 11

[A S]

Attachment: screenshot2

Comment 12

[A S]

Attachment: screenshot3

last one, sorry for generating so many emails to everyone

Comment 13

[Mike Connor [:mconnor]]

this is fixed on trunk, but not on the branch 1.0 will be released from.  The
fix caused too many regressions elsewhere to be considered for a "stable" branch.

Comment 14

[Ben Claar]

I don't understand two things.. why is this bug marked "RESOLVED WORKSFORME"
when you say it has been fixed?  If it's been fixed, it should be marked
"FIXED".  I'm using Firefox 1.0 on WinXP and I see this bug approximately 1/3 of
the time.

You say this fix isn't in the 1.0 branch.. so when can Firefox expect to see
this fixed

Comment 15

[Martijn Wargers (dead)]

No, it should probably have been a duplicate of the bug mentioned in comment 1,
but it was reopened again since then.

In the next release (1.1 or something like that), Firefox will have this fix.