Bug 15866 - The image is not showing if the background property has the values in this order: background: url center no-repeat top
Summary: The image is not showing if the background property has the values in this or...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL: http://love.qihoo.com/
Keywords: HasReduction
Depends on:
Blocks:
 
Reported: 2007-11-06 20:40 PST by Anantha Keesara
Modified: 2008-05-06 11:23 PDT (History)
3 users (show)

See Also:


Attachments
reduced test in strict mode (document.compatMode == "CSS1Compat") (704 bytes, text/html)
2008-01-17 04:08 PST, Eric Seidel (no email)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anantha Keesara 2007-11-06 20:40:46 PST
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
Comment 1 Anantha Keesara 2007-11-06 20:56:38 PST
tested with webkit version:27433
Comment 2 Dave Hyatt 2007-11-07 10:06:21 PST
This bug seems invalid to me.  You can't separate center and top, since they are part of a single prop, background-position.
Comment 3 Dave Hyatt 2007-11-07 10:10:34 PST
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.


Comment 4 Eric Seidel (no email) 2008-01-17 04:08:37 PST
Created attachment 18499 [details]
reduced test in strict mode (document.compatMode == "CSS1Compat")
Comment 5 Eric Seidel (no email) 2008-01-17 04:09:36 PST
We'll need to test IE's behavior with this test case.  This test demonstrates that gecko has this "bug" even in strict mode.
Comment 6 Dave Hyatt 2008-01-17 10:46:33 PST
This seems invalid to me, unless we want to try to do a quirk.

Comment 7 Eric Seidel (no email) 2008-01-17 11:41:35 PST
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.
Comment 8 Darin Fisher (:fishd, Google) 2008-01-17 21:54:10 PST
FYI, FF3 (b2) seems to match WebKit.
Comment 9 Jeff Walden (remove +bwo to email) 2008-01-17 22:44:39 PST
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.
Comment 10 Eric Seidel (no email) 2008-05-06 11:23:42 PDT
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.