293746 - Background image style aplied to the window element break painting

Status: RESOLVED WONTFIX

(Core Graveyard :: GFX, defect)

Description

[Anders Conbere]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050428 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050428 Firefox/1.0.3

When the window element is assigned the background: value of a png file. The
browser to draw all elements and is generaly laggy and broken. This apears to
only be an issue with chrome, any content with this style works fine.

Reproducible: Always

Steps to Reproduce:
<described at webpage>

Actual Results:  
Browser elements fail to paint.

Expected Results:  
Theoreticaly the browser should display the the window elements with the png
background with little or no trouble.

Comment 1

[Tristor]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050511
Firefox/1.0+

Wow, that was seriously messed up.  On win32, this not only causes the things
specified in this report, but also makes FF ignore the screenspace assigned to
it and draw overtop the Windows taskbar.  FF stopped responding and had to be
closed from the task manager (I could have alt+f4ed maybe, but I didn't try
that).  I have a screencap of the effect on my system if it is needed.  Is this
possibly a regression from a recent check-in?  Changed OS to All.  Anybody know
which product/component this belongs in, because I am pretty sure it isn't
Firefox/General.

Comment 2

[Tristor]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050511

I confirm this happening on Seamonkey trunk as well.  Per kbrosnan's suggestion,
I am moving this to Core:GFX.

Comment 3

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

Someone needs to isolate the regression window

Comment 4

[Wolf [:wolf]]

Builds from 04/01 (and possibly before, but later than 3/1) - 04/14 (to
somewhere between 04/14 and 05/01) crash instead. Same testcase. (TB5769204Y,
TB5769194G).

So far, i'm able to reproduce this all the way back to 02/01.

Comment 5

[Wolf [:wolf]]

I've tested builds (jumping back, several weeks at a time) all the way to
2004-11-10. They're all broken with the testcase, in similar ways. (High CPU
Use, Hanging, Crashing, Missing Elements, etc.) I'm not sure when this broke,
but its either awhile ago, or something went weird during my testing.
(Firefox-Trunk/WinXP Pro)

Comment 6

[Anders Conbere]

I just got done testing this with a .gif background

http://www.bytecave.net/anders/test_background.gif

and the same effects are observed as resutl I've changed the title of the bug to
"image styles".

Comment 7

[Anders Conbere]

And due to my own lack of foresight,

the same is again true for .jpg files.

http://www.bytecave.net/anders/test_background.jpg

Comment 8

[Anders Conbere]

I've been made aware of a work around for this bug.

By simply applying a background color to the window element along with an image,
the browser behaves normaly.

an example userChrome entry is as follows

window{ background: #000000 url("test_background.png") fixed top !important; }

Though I still feel the browser should be able to handle the style without this
workaround, at least it can easily be bypassed.

Comment 9

[Andrew Schultz]

there's no regression here.  in fact, setting a background seems to trigger the
transparent XUL code, which (until recently) was hosed, so older builds just
blow up completely (or at least do /really/ strange things).

Also (from the URL), to reproduce this bug, add this to your userChrome.css:

window{ background: url("test_background.png") fixed top !important; }
(test_background.png can be any image)

Comment 10

[Tristor]

(In reply to comment #9)
> there's no regression here.  in fact, setting a background seems to trigger the
> transparent XUL code, which (until recently) was hosed, so older builds just
> blow up completely (or at least do /really/ strange things).
> 
> Also (from the URL), to reproduce this bug, add this to your userChrome.css:
> 
> window{ background: url("test_background.png") fixed top !important; }
> (test_background.png can be any image)

According to the reporter, it only occurs on Trunk builds, and not on milestone
builds, so that would lead me to believe that somewhere something was broken
that wasn't broken when 1.0 branched.

Comment 11

[Gordon P. Hemsley [:GPHemsley]]

This bug has been buried in the graveyard and has not been updated in over 5 years. It is probably safe to assume that it will never be fixed, so resolving as WONTFIX.

[Mass-change filter: graveyard-wontfix-2014-09-24]