467624 - background-position is messed up (background-image is moved by a wrong distance)

Status: RESOLVED FIXED

(Core :: Layout, defect)

Description

[Andreas Jung]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081202 Shiretoko/3.1b3pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081202 Shiretoko/3.1b3pre

In the newest nightlies I noticed that Minefield/Shiretoko displays a background-image which is moved with background-position wrong.
It seems to move the background-image by a wrong (too large) distance.
I'll attach a testcase...

Reproducible: Always

Steps to Reproduce:
1.open the testcase
2.
3.
Actual Results:  
Background-image is displayed wrong / moved by wrong distance.

Expected Results:  
Background-image is displayed correct.

Comment 1

[Andreas Jung]

Attachment: testcase

Comment 2

[Andreas Jung]

Attachment: Firefox 3.0.4 (correct)

Comment 3

[Andreas Jung]

Attachment: Shiretoko 3.1b3pre (wrong)

this is how it is displayed in Shiretoko 3.1b3pre (wrong)

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081202 Shiretoko/3.1b3pre

Comment 4

[Robert O'Callahan (:roc) (email my personal email if necessary)]

WFM on Mac. Windows only? Probably the same as 466258 if it goes away when you remove the border.

Comment 5

[Andreas Jung]

Border and margin was only added to make it clearer / more comfortable for the eyes.
It is still reproducible if the border and/or margin is removed.

(What is 466258 about anyway? Bugzilla tells me I'm not authorized to access that bug...)

Comment 6

[Andreas Jung]

Attachment: testcase without border and margin

Comment 7

[Brian Polidoro]

This is broken starting with the 11-05 build.
http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2008-11-04+03%3A00%3A00&enddate=2008-11-05+03%3A00%3A00

Bug 458487? which seems like Roc was on the right track. So maybe this is the same as bug 467029. There is transparency in the gif used in this testcase.

Comment 8

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Seems to be fixed by the patch in bug 466258.

Comment 9

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Should be fixed on trunk by the fixing of bug 466258.