Last modified: 2012-05-30 02:39:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T36551, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34551 - CSS rule causes blue background for chrome users
CSS rule causes blue background for chrome users
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://code.google.com/p/chromium/iss...
: upstream
: 34444 36082 36219 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-20 19:30 UTC by Joey Smith
Modified: 2012-05-30 02:39 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
screenshot of bug (73.68 KB, image/png)
2012-02-20 19:30 UTC, Joey Smith
Details

Description Joey Smith 2012-02-20 19:30:30 UTC
Created attachment 10053 [details]
screenshot of bug

http://bits.wikimedia.org/en.wikipedia.org/load.php?debug=false&lang=en&modules=ext.wikihiero%7Cmediawiki.legacy.commonPrint%2Cshared%7Cskins.vector&only=styles&skin=vector&* is a WP CSS stylesheet with a very odd bug in it, that is beginning to bite more and more Chrome users - it has the same two 'background-image' rules, one right after the other, on 3 nodes: div#content, #mw-head-base, and div#footer:


background-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAIAAACQd1PeAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAABhJREFUeF4FwTEBAAAAgjD7FzESWfjYdgwEoAJ4lTsaxgAAAABJRU5ErkJggg==);background-image: url(//bits.wikimedia.org/skins-1.18/vector/images/border.png?2011-09-19T16:11:40Z)!ie;


Recent Chrome ignores the second background-image rule and thus gives an ugly blue tint behind the aforementioned nodes (see attachment)
Comment 1 Joey Smith 2012-02-20 19:31:51 UTC
You can find a bug on this from the Chrome side at http://code.google.com/p/chromium/issues/detail?can=2&start=0&num=100&q=&id=113711
Comment 2 MZMcBride 2012-02-20 19:36:11 UTC
(In reply to comment #0)
> Recent Chrome ignores the second background-image rule and thus gives an ugly
> blue tint behind the aforementioned nodes (see attachment)

Can you be a bit more specific about this? Which version of Chrome are you using and on which OS?
Comment 3 Derk-Jan Hartman 2012-02-20 20:19:42 UTC
those elements have; background-repeat: repeat-y; after those statements.

Judging from the screenshot, the browser acts as if repeat-x is set as well, possibly it's (incorrectly) ignoring all CSS elements after the line with the !ie hack ?
Comment 4 Joey Smith 2012-02-21 04:59:09 UTC
It's not the '!ie' hack - I've confirmed that Chrome exhibits the same behaviour even if you load a version of the stylesheet without this hack. However, it does appear to be related to zoom level.
Comment 5 Sertmann 2012-02-23 17:21:22 UTC
I'm having the same issue with 18.0.1025.39 beta-m on Windows 7
Comment 6 Erwin Dokter 2012-03-31 15:13:31 UTC
This is a Chrome bug introduced in Chrome 18. There is nothing wrong with the CSS, as any permutation of the CSS rule results in the bug being displayed. In essense, Chrome seems to ignore or mis-interpret the repeat-x/y attributes when the zoom level is below 100%. Short term fix: use 100% zoom level. There is nothing we can do about it, so I'm closing this as INVALID.
Comment 7 Tisza Gergő 2012-04-09 16:35:35 UTC
*** Bug 34444 has been marked as a duplicate of this bug. ***
Comment 8 Michael M. 2012-04-19 09:09:58 UTC
*** Bug 36082 has been marked as a duplicate of this bug. ***
Comment 9 Michael M. 2012-04-25 07:45:36 UTC
*** Bug 36219 has been marked as a duplicate of this bug. ***
Comment 10 Chris 2012-05-30 02:39:07 UTC
Chrome seems to have fixed the bug. (on Windows XP)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links