Closed Bug 300793 Opened 19 years ago Closed 18 years ago

There is a big text area whose bottom half is covered with black. Selecting/highlighting the text allows one to see it. Page displays fine in IE.

Categories

(Tech Evangelism Graveyard :: English US, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: pgmer6809, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

The text beginning: A day shy of the second anniversary ....
only displays up to: ... wins seventh yellow jersey without winning ...
The portion after that to the end is covered with a big black area. 
However highlighting the text under the black area, allows one to read it up to
the end: ... which appears on his sponsor's t-shirts.

All of the problem text is in a <div id> ... </div> tag.

View source of the page works fine.

Reproducible: Always

Steps to Reproduce:
1. Go to the OLN web site.
2. select the current stage (or any stage) then the WRAPUP tab.
3. scroll down. The bottom part of  text is obscured. Hightlight the black area.
text is revealed.

Actual Results:  
Text is revealed.

Expected Results:  
display text the way IE does.
confirmed Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3)
Gecko/20050711 Firefox/1.0+

But this could be a Tech Evang issue.
This is probably tech evangelism. The content is all left or right floats, they
don't take up any room for the containing block. The only reason why it is at
least 880px, is because of the min-height:880px;
Assignee: nobody → english-us
Component: General → English US
Product: Firefox → Tech Evangelism
QA Contact: general → english-us
Pages now work as they should, closing as WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.