Closed Bug 3672 Opened 26 years ago Closed 26 years ago

[BLOCK] throbber: titlebutton ignores list-style-image

Categories

(Core :: XUL, defect, P2)

x86
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: slamm, Assigned: eric)

Details

If the throbber sets the src attribute in xul, then the image does not change when "busy" changes. If I take out the src attribute, then the button does not show an image at all. Is my syntax correct, or is this really broken? Here is my css fragment: button.throbber { width: 32px; height: 32px; background-color:red; list-style-image: url("resource:/res/throbber/anims06.gif"); } titlebutton[busy]#throbber { list-style-image: url("resource:/res/throbber/anims06.gif"); } titlebutton#throbber { list-style-image: url("resource:/res/throbber/anims00.gif"); } Here is my xul fragment: <titledbutton id="throbber" busy="false" align="right" onClick="window.frames[0].home()"/> Here's the js function that sets the busy attribute (this function does get called at the appropriate times): function SetThrobberBusy() { dump("+++++++ In javascript function: SetThrobberBusy()\n ++++++++"); var throbber = document.getElementById("throbber"); if (throbber != null) { dump("+++++++ In javascript function: SetThrobberBusy(), setting busy attribute to true\n ++++++++"); /* throbber.setAttribute("src", "resource:/res/throbber/anims06.gif");*/ throbber.setAttribute("busy", "true"); dump("Done setting busy attribute to true\n"); } }
Priority: P3 → P2
Target Milestone: M3
setting p2 for m3
QA Contact: 4150 → 3849
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
The following XUL fragment is not correct. I have mailed you the correct one.
who fixed this bug? what did you do to fix it?
The XUL fragment example was wrong that created this bug. Look at navigator.xul and the way the throbber is hooked up. It uses list-style-image to change the titledbuttons image and it works.
Status: RESOLVED → VERIFIED
cool -- so I'll mark this verified based on developer input.
You need to log in before you can comment on or make changes to this bug.