Closed Bug 611321 Opened 10 years ago Closed 10 years ago

Port progressmeter element to addonbar as button overlay using loading.png

Categories

(Firefox :: Toolbars and Customization, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: pwd.mozilla, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101110 Firefox/4.0b8pre
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101110 Firefox/4.0b8pre

The <progressmeter> is traditionally in in the statusbar and as such can appear on the shim, but it should be ported to the addonbar as an overlay that can placed over a button on command.

Reproducible: Always
Blocks: 574688
OS: Windows 7 → All
Hardware: x86 → All
Version: unspecified → Trunk
Forgot to mention that while a pie-chart would perhaps be the best option for this, we can simply use chrome://browser/skin/tabbrowser/loading.png
in case you mean the progressmeter the extension status-4-evar provides, this is not gonna happen. use this extension instead. if not: what do you mean?
(In reply to comment #2)
> in case you mean the progressmeter the extension status-4-evar provides, this
> is not gonna happen. use this extension instead. if not: what do you mean?

https://developer.mozilla.org/en/XUL/progressmeter
This is not going to be in the add-on bar by default. Using an extension to replace this functionality is correct route to take here.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Dietrich. I'm not talking about the progress of a page here. I'm talking about the pregressmeter element which an extension may invoke to show something is happening by the extension. I'm pretty sure it's hackable, but the fact it was on the original statusbar for extension developers shows that it was thought handy and I know a fair few extensions that use it. It would make sense to have some sort of API for it.
That's a great idea. It should be implemented as a Jetpack JS module though, still not something we'd fix in Firefox itself.
You need to log in before you can comment on or make changes to this bug.