Bug 15866 – The image is not showing if the background property has the values in this order: background: url center no-repeat top

• Component: CSS
• Status: RESOLVED INVALID

[Anantha Keesara]

I .Steps:
-----------
1. Go to: http://love.qihoo.com/

II. Issue:
-----------------
In Safari, the link right beside the flower borders is not visible. 
Screenshot: http://help.improve.safari.googlepages.com/issue.jpg

III. 
Behavior in other browsers :
------------------------------
FF ,IE   : link visible
Safari, Opera  : link not visible

III. reduction:
---------------
 http://help.improve.safari.googlepages.com/mytest.html

[Anantha Keesara]

tested with webkit version:27433

[Dave Hyatt]

This bug seems invalid to me.  You can't separate center and top, since they are part of a single prop, background-position.

[Dave Hyatt]

We could consider a quirk once we understand what IE and Gecko are doing wrong.  Might be worth seeing if Gecko behaves in strict mode.  Then we'd know it's an IE quirk and not just a Gecko bug.

[Eric Seidel (no email)]

Created attachment 18499 [details]
reduced test in strict mode (document.compatMode == "CSS1Compat")

[Eric Seidel (no email)]

We'll need to test IE's behavior with this test case.  This test demonstrates that gecko has this "bug" even in strict mode.

[Dave Hyatt]

This seems invalid to me, unless we want to try to do a quirk.

[Eric Seidel (no email)]

The way we would decide whether to do this quirk or not, is really just how popular this usage is.  It seems like rather a benign quirk to implement, but w/o a justifiable heavy usage in real pages, it's not worth the time.

[Darin Fisher (:fishd, Google)]

FYI, FF3 (b2) seems to match WebKit.

[Jeff Walden (remove +bwo to email)]

This got fixed in <https://bugzilla.mozilla.org/show_bug.cgi?id=258080> with a regression test for this specific behavior, so I think it unlikely it was an IE quirk.  There don't seem to have been any site-incompatibility reports either over the change.

[Eric Seidel (no email)]

Based on hyatts comments above, and my own sentiment.  This was a FF and IE bug.  FF has fixed their bug.  We won't match IE's broken behavior in strict mode.  Invalid.