Closed Bug 317679 Opened 20 years ago Closed 20 years ago

Background image is not at the bottom as defined in CSS file

Categories

(Core :: CSS Parsing and Computation, defect)

1.8 Branch
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 243751

People

(Reporter: swen.bmn, Assigned: dbaron)

References

()

Details

(Keywords: css2)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 If you compare this URL in Firefox 1.x, Safari and Mozilla, the background image is not correctly positioned in Firefox 1.5 RC1,2,3. You can see it if you scroll down. In Firefox 1.5 the image goes up but it should stay at the bottom. Reproducible: Always Steps to Reproduce: 1.Open the URL in browser 2.Scroll down browser windows if no scrollbar, make browser windows smaller 3. Actual Results: Wrong behaviour in Firefox 1.5 and Opera. Right behaviour in Firefox 1.x, Safari, Mozilla, IE6 Expected Results: Background image should stay at the bottom. Look at the end of https://bugzilla.mozilla.org/show_bug.cgi?id=316001
You can see a similar error on http://www.dellwebsites.com/web/box/bottomleft.html With Firefox 1.x the background image is visible. With Opera 8.51 and Firefox 1.5 it is gone!
Keywords: css2
Sorry, with Firefox 1.5 RC3 the rose is not at the bottom as it should. See: http://www.dellwebsites.com/web/box/bottomleft.html
Assignee: nobody → dbaron
Component: General → Style System (CSS)
Product: Firefox → Core
QA Contact: general → ian
Version: unspecified → 1.8 Branch
The behavior of Firefox 1.5 and Opera 8.5 is correct per the CSS2.1 spec. The other browsers are buggy.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
*** This bug has been marked as a duplicate of 243751 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.