Closed
Bug 500480
Opened 16 years ago
Closed 16 years ago
unable to install add-ons extensions
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jmaher, Assigned: vingtetun)
Details
Attachments
(1 file, 1 obsolete file)
|
4.04 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
on both maemo and winmo (beta2 build1), I got to add-ons manager search for script, get no-script and AutoPager. I click the install button and I get the top part of a grey box, but I cannot scroll into it. This is the case for both of the mentioned add-ons.
Comment 1•16 years ago
|
||
I went to the extensions panel in options, searched for "script" and installed no script there with no problems.
Comment 2•16 years ago
|
||
This is on my n810 with Maemo.
| Assignee | ||
Comment 3•16 years ago
|
||
In fact the extension should install, the top bar seen is a progress element that should display the current download progress.
The progress display have been broken here http://hg.mozilla.org/mobile-browser/rev/5bbb4c203890
The patch basically revert the extensions.js change done in this changeset to show how it should work.
It is not the good way to do since we already have an observer for the xpi download progress.
Mark, you probably know this part very well, any hint?
Comment 4•16 years ago
|
||
I switched to weak references purely so I wouldn't need to un register. But since we have an ExtensionsView.uninit() and, more importantly, the code is broken - we should change back :)
Updated•16 years ago
|
Attachment #385292 -
Flags: review+
Comment 5•16 years ago
|
||
(In reply to comment #3)
> It is not the good way to do since we already have an observer for the xpi
> download progress.
What is "not a good way"?
| Assignee | ||
Comment 6•16 years ago
|
||
(In reply to comment #5)
> (In reply to comment #3)
>
> > It is not the good way to do since we already have an observer for the xpi
> > download progress.
>
> What is "not a good way"?
I saying that cause browser.js#173 already do os.addObserver(gXPInstallObserver, "xpinstall-download-started", false); but its like gXPInstallObserver do nothing on this topic.
Not sure why it is here?
| Assignee | ||
Comment 7•16 years ago
|
||
Ok, now I see what it is for in browser.js after have read your comments on bug 437959.
I supposed it is unused now but it can be in the future.
Comment 8•16 years ago
|
||
Ah, I see what you mean now. We really only need to handle "xpinstall-install-blocked" in browser.js for now.
Comment 9•16 years ago
|
||
Can you remove the addEventListener / removeEventListener in this patch ?
| Assignee | ||
Comment 10•16 years ago
|
||
do you mean addInstallListener/removeInstallListenerAt?
Comment 11•16 years ago
|
||
| Assignee | ||
Comment 12•16 years ago
|
||
Yes :)
Assignee: nobody → 21
Attachment #385292 -
Attachment is obsolete: true
Attachment #386240 -
Flags: review?(mark.finkle)
Updated•16 years ago
|
Attachment #386240 -
Flags: review?(mark.finkle) → review+
Comment 13•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•