Closed Bug 111451 Opened 23 years ago Closed 22 years ago

CSS and div block render problem on reload

Categories

(Core Graveyard :: GFX, defect, P1)

defect

Tracking

(Not tracked)

CLOSED WORKSFORME
Future

People

(Reporter: lars, Assigned: kmcclusk)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011121
BuildID:    0.9.6

The page http://evaspoint.sf.net do not render correct on reload. The backgound
image of a link covers the other div blocks. It looks like mozilla is skipping
some render steps on reload and when showing a new page on the same site. The
page validates for both CSS2 and HTML4.

Reproducible: Sometimes
Steps to Reproduce:
Reproduce by reloading the page a couple of times.

Actual Results:  Links background covers other div blocks.

Expected Results:  Links background should not cover other div blocks.
seeing this in current nightly build too.  Compositor
Assignee: dbaron → kmcclusk
Status: UNCONFIRMED → NEW
Component: Style System → Compositor
Ever confirmed: true
QA Contact: ian → petersen
This seems more likely to be an invalidation problem in the layout code or the
image code.  Are we not invalidating the right area when a background image load
comes in?
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0.1
I've encountered other stylesheet related bugs at these pages:

bug 120370 - http://www.codeprpject.com (klick a artical and sometimes the <pre>
blocks are wrong size)

no bug - http://www.slayerweb.com (originally opk - but then spaces in the
tables - the site uses also stylesheet)
I forgot that the bug 120370 is 'reload fixable'
Bulk moving Mozilla1.01 bugs to future-P1. I will pull from the future-P1 list
to schedule bugs for post Mozilla1.0 milestones
Priority: -- → P1
Target Milestone: mozilla1.0.1 → Future
WFM: Using 2002070204 build on WinXP. A month or so ago I changed the background
image rendering to display the background only after the entire background was
loaded instead of displaying it incrementally. That change may have fixed this bug. 
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Yes, the page has been working for over a month. Thanks.
Status: RESOLVED → CLOSED
CLOSED is deprecated.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.