Missing progressmeter-busy.gif referenced from chrome://global/skin/tree.css

RESOLVED FIXED in Firefox 52

Status

()

RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: florian, Assigned: florian)

Tracking

unspecified
mozilla52
Points:
---

Firefox Tracking Flags

(firefox52 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

2 years ago
From bug 1221383: missing chrome://global/skin/progressmeter/progressmeter-busy.gif referenced from chrome://global/skin/tree.css

This is on Linux/Windows. On Mac the same rule is empty and commented out.

I got a little bit lost in the history, but here is what I found:
- This file exists for SeaMonkey.
- For Firefox it existed in the qute theme, but never seem to have existed in the winstripe theme. See http://hg.mozilla.org/experimental/gecko-dev/rev/09ccd0a7044b

So it seems this has been broken in toolkit since 2004; seems safe to remove the rules.
(Assignee)

Comment 1

2 years ago
Created attachment 8795317 [details] [diff] [review]
Patch
Attachment #8795317 - Flags: review?(gijskruitbosch+bugs)
(Assignee)

Updated

2 years ago
Assignee: nobody → florian
Status: NEW → ASSIGNED

Comment 2

2 years ago
Comment on attachment 8795317 [details] [diff] [review]
Patch

Review of attachment 8795317 [details] [diff] [review]:
-----------------------------------------------------------------

It once existed even for toolkit/skin/win/ (check mozilla1.7 on dxr) but I don't think it matters anymore.
Attachment #8795317 - Flags: review?(gijskruitbosch+bugs) → review+
(Assignee)

Comment 3

2 years ago
https://hg.mozilla.org/integration/fx-team/rev/67ce36549b92124d08004544dd0ddde72ff7b476
Bug 1305724 - Missing progressmeter-busy.gif referenced from chrome://global/skin/tree.css, r=Gijs.

Comment 4

2 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/67ce36549b92
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
status-firefox52: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
Component: XUL → Themes
Product: Core → Toolkit
You need to log in before you can comment on or make changes to this bug.