Closed
Bug 924111
Opened 11 years ago
Closed 7 years ago
localized addon's preferences stops working after disable button is pressed
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: backy0175, Assigned: evold)
References
Details
Attachments
(2 files)
I am testing localized addon's preferences and found a problem.
once addon disabled, localized addon's preferences stops working
until reboot Firefox.
here are steps to reproduce problem.
test1: enable -> disable -> enable -> reboot Firefox
start Firefox
open Add-ons Manager
press options button -> displyed localized preferences
press disable
press enable -> displayed NOT localized prefences
stop Firefox
start Firefox
open Add-ons Manager
press options button -> displyed localized preferences
test2: disabled -> enable
start Firefox
open Add-ons Manager
press options button -> displyed localized preferences
press disable
stop Firefox
start Firefox
open Add-ons Manager
press enable -> displayed localized preferences
Can you attach a minimal add-on to test, please.
Flags: needinfo?(backy0175)
Hi Loic.
Thank you for your respond and I'm sorry at the lack of information.
I attached my test addon that created Add-on Builder and add some locale json files manually.
Background:
1. Add-on Builder do not support localizable addon.
mozilla Add-ons Forum "Can't build localizable addons on Add-on Builder"
https://forums.mozilla.org/addons/viewtopic.php?f=27&t=14535
2. I'm trying to find a way to create localizable addon with Add-on Builder.
3. I checked inside l10n modules on Add-on SDK, then I found Add-on SDK is using some json files to support localization.
4. I added some locale json files into addon package file(xpi)
my-addon/
data
lib
locale/
en-US.json
it.json
ja-JP.json
locales.json
5. This works fine. But localized addon's preferences stops working after disable button is pressed.
Flags: needinfo?(backy0175)
I did additional tests and found a cause.
This problem is happen ONLY on my Firefox environment for development.
What I did.
Test3. Create test addon by cfx. -> happened same problem.
Test4. Do locale test on other (more clean) Firefox environment. -> NOT happend this problem.
I'm sorry for taking your time.
backy0175
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
I'm still fighting with this problem. :-(
Test5:
Create new profile on my Firefox environment for development.
Install locale test addon which was built by cfx -> still happend same problem.
Test6:
Disalbe all plugins on new profile -> still happend same problem.
Moving to Add-on SDK, I guess it's a better component.
Status: RESOLVED → UNCONFIRMED
Component: Add-ons Manager → General
Product: Toolkit → Add-on SDK
Resolution: WORKSFORME → ---
Version: 24 Branch → unspecified
Needinfoing Dave to remind him to find that other bug to set up the dependency.
Flags: needinfo?(dtownsend+bugmail)
Priority: -- → P2
Comment 7•11 years ago
|
||
This is likely because the localisation code is asynchronous but the add-ons manager expects the add-on to initialise synchronously. We'd need that to be fixed first before we could fix this.
Depends on: 771441
Flags: needinfo?(dtownsend+bugmail)
I see.
It is seemed to have stopped working because it is asynchronous.
Then fixed this problem by close and re-open Add-ons Manager.
Test6:
open Add-ons Manager
disable addon
enable addon -> displayed NOT localized prefences
close Add-ons Manager
open Add-ons Manager
press options button -> displyed localized preferences
Correction.
> Then fixed this problem by close and re-open Add-ons Manager.
Then avoid this problem by close and re-open Add-ons Manager.
Comment 10•11 years ago
|
||
Yeah that matches what I'd expect. We might be able to hack around this by forcing the add-ons manager to refresh after the localisation info is loaded.
Assignee | ||
Updated•10 years ago
|
Blocks: sdk/simple-prefs
Assignee | ||
Comment 11•10 years ago
|
||
I'm going to take a look at this one, it seems odd.
Assignee: nobody → evold
Comment 12•7 years ago
|
||
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago → 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•