291221 - CSS attribute background-attachment always anchors to the page as a whole

Status: VERIFIED DUPLICATE of bug 119518

(Core :: Layout, defect)

Description

[Kirsle]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

On a website layout I was working on recently, I attempted to use the CSS
attribute "background-attachment: fixed" within a cell in one of the tables.
Other browsers (namely Internet Explorer) render this correctly: the page can
scroll up and down, but the background image is fixed within its space in the
table. However, Firefox anchors the image in relation to the page and not to the
cell in the table. So, inside the table cell you can see what background would
be visible, and scrolling the page up and down scrolls the table, but the
background within the table is still fixed in relation to the page behind it.

For example, http://69.246.67.30/index.cgi (it's on my local testing server).
I'll try to keep the "broken" example up as long as possible. The solution I
found was to use an absolutely-positioned <div> to give the effect of a fixed
background image (as on http://aichaos.com/ ).

Reproducible: Always

Steps to Reproduce:
1. Visit any website that uses background-attachment:fixed in unusual places
(i.e. table cells or <div>'s, as opposed to the BODY tag).
Actual Results:  
The background image was fixed in relation to the document, not to the table
cell it was in (a way of thinking about it, the table cell would have been like
a window to see behind the page, where the background image was visible, and
scrolling the page up and down was like moving the window up and down).

Expected Results:  
It should have had coordinate (0,0) of the image be aligned to the top left
corner (0,0) of the table cell it was in, instead of (0,0) of the document as a
whole.

Comment 1

[Richard Brodie]

Commendably clear bug report; however, Firefox is doing the right thing here.

*** This bug has been marked as a duplicate of 119518 ***