Closed Bug 462720 Opened 17 years ago Closed 17 years ago

CSS: background-position: center bottom; wrong positioned and shrunken.

Categories

(Firefox :: General, defect)

x86
macOS
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 243751

People

(Reporter: bugzilla, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.3) Gecko/2008092414 Firefox/3.0.3 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.3) Gecko/2008092414 Firefox/3.0.3 For reproducing this bug: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>background-image</title> <style> body { background-image: url("image.jpg"); background-position: center bottom; background-repeat: no-repeat; } </style> </head> <body> </body> </html> Reproducible: Always Steps to Reproduce: 1. Make a test with the given example. 2. 3. Actual Results: The image is positioned at the top instead of bottom and shrunken. Expected Results: Image should be positioned at the bottom an right sized. This bug is reproducible with FF 3.0.3 under MAC OS X, Windows and Linux
Invalid, "bottom center" is the correct setting... http://www.w3.org/TR/CSS1/#background-position
(In reply to comment #1) > Invalid, "bottom center" is the correct setting... > http://www.w3.org/TR/CSS1/#background-position ahem, per CSS 2.1 http://www.w3.org/TR/CSS21/colors.html#propdef-background-position that part is perfectly valid. But this is invalid for another reason. Given the testcase, the body is empty, and is only the size of its margins. Add a border-bottom to your body element, and you'll see how tall it is. The position of the background image is correct according to the CSS specs <http://www.w3.org/TR/CSS21/colors.html#background>
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
(In reply to comment #2) > ahem, per CSS 2.1 > http://www.w3.org/TR/CSS21/colors.html#propdef-background-position > that part is perfectly valid. <sheepish> ;-) My Bad...
You need to log in before you can comment on or make changes to this bug.