Closed Bug 641977 Opened 15 years ago Closed 15 years ago

background-size does not function when using background shorthand for the image

Categories

(Core :: Layout, defect)

x86
macOS
defect
Not set
minor

Tracking

()

RESOLVED INVALID

People

(Reporter: terwey, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16 Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0 When using a background: url(path/to/image.ext); in combination with background-size: 80%; the size does not change. When using the background-image it functions. Reproducible: Always Steps to Reproduce: check the details, can be reproduced all the time Expected Results: resize the background image
More accurately, the 'background' shorthand is resetting the 'background-size' property, in violation of the CSS3 B&B spec. It may also be resetting other inappropriate background-* properties, but I have not tested them.
Which did you put first? If you put background-size before background, then the shorthand is supposed to reset background-size (contrary to what Tab says, which is wrong). (We don't yet support the syntax for including background-size in the shorthand; I don't believe it's yet reached Candidate Recommendation, but it hopefully will do so soon.)
Wait, what? I swear I read the property description and didn't see 'background-size' there in the list of properties that were reset. Never mind, then. :/
Reporter, can you please attach a testcase showing the problem?
And in particular, my attempt to reproduce doesn't; I see the image at the scaled-down size if I put background-size after background.
Then I'm going to mark the bug as invalid on the assumption that the reporter was putting 'background-size' before (or at lower specificity than) 'background'. If that's not the case, please reopen the bug report.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.