Closed
Bug 675371
Opened 13 years ago
Closed 13 years ago
load/unload chrome.manifest files for bootstrapped addons automatically
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
FIXED
mozilla10
People
(Reporter: davemgarrett, Assigned: darktrojan)
References
Details
(Keywords: dev-doc-complete)
Attachments
(2 files, 2 obsolete files)
6.56 KB,
patch
|
mossop
:
review+
|
Details | Diff | Splinter Review |
7.77 KB,
patch
|
Details | Diff | Splinter Review |
Bug 564667 added the capability to load/unload a chrome.manifest file dynamically for bootstrapped addons. This follow up bug is for implementing a system to automatically detect chrome.manifest and load/unload as needed it to avoid unnecessary boilerplate code to do so in bootstrap.js files.
Comment 1•13 years ago
|
||
I can take this one, I'll have a look on Monday.
Updated•13 years ago
|
Assignee: nobody → colmeiro
Reporter | ||
Comment 2•13 years ago
|
||
Thanks. If possible, it would be nice to have this land before the next milestone so addons that want to use this and support Gecko 8 & 9 won't have to do things differently for each.
Comment 3•13 years ago
|
||
I'd use this to make all our langpacks bootstrapped?
Comment 4•13 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #3) > I'd use this to make all our langpacks bootstrapped? That is one option, the other is to treat langpacks as a special case like we plan to for dictionaries in bug 591780
Comment 5•13 years ago
|
||
(In reply to Dave Townsend (:Mossop) from comment #4) > (In reply to Axel Hecht [:Pike] from comment #3) > > I'd use this to make all our langpacks bootstrapped? > > That is one option, the other is to treat langpacks as a special case like > we plan to for dictionaries in bug 591780 Better still, filed bug 677092 on that.
Reporter | ||
Comment 6•13 years ago
|
||
Hernán, have you had a chance to look at this yet? The next merge is approaching and without this using chrome with bootstrapped addons will have a backwards compatibility issue once this is eventually done.
Comment 7•13 years ago
|
||
(In reply to Dave Garrett from comment #6) > Hernán, have you had a chance to look at this yet? The next merge is > approaching and without this using chrome with bootstrapped addons will have > a backwards compatibility issue once this is eventually done. No, I couldn't look at this properly, I had a busy week. I'm taking a look now and I'll hope to get it before the next merge :)
Assignee | ||
Comment 8•13 years ago
|
||
I've created functions for startup and shutdown of bootstrapped addons. This will also be useful for fixing bug 542385, bug 675372 and friends.
Assignee: colmeiro → geoff
Attachment #564355 -
Flags: review?(dtownsend)
Comment 9•13 years ago
|
||
What is the need for creating the new methods like that? I'm not sure I see how it will help the bugs you mention.
Assignee | ||
Comment 10•13 years ago
|
||
I actually meant bug 564675, not 542387. And I'm not sure about bug 675372. My theory was that it'd be better to make any required changes for them in one place instead of several. I'm probably just overthinking things again.
Comment 11•13 years ago
|
||
Perhaps. I think for now though we can just keep this simple by testing for "startup" and "shutdown" in callBootstrapMethod. You'll find that will not bitrot from bug 591780 quite so badly either ;) Make that change and I'll go over it again to read the test in more detail but otherwise this looks good.
Assignee | ||
Comment 12•13 years ago
|
||
So, back to my original plan then.
Attachment #564355 -
Attachment is obsolete: true
Attachment #564355 -
Flags: review?(dtownsend)
Attachment #565400 -
Flags: review?(dtownsend)
Comment 13•13 years ago
|
||
Comment on attachment 565400 [details] [diff] [review] patch v2 Review of attachment 565400 [details] [diff] [review]: ----------------------------------------------------------------- I'd really rather you just added a test for the method name in callBootstrapMethod and called addBootstrappedManifestLocation or removeBootstrappedManifestLocation as appropriate there so we don't have to remember to do it at all call sites
Attachment #565400 -
Flags: review?(dtownsend) → review-
Assignee | ||
Comment 14•13 years ago
|
||
(In reply to Dave Townsend (:Mossop) from comment #13) > I'd really rather you just added a test for the method name in > callBootstrapMethod and called addBootstrappedManifestLocation or > removeBootstrappedManifestLocation as appropriate there so we don't have to > remember to do it at all call sites *facepalm* That would be the logical thing to do, and what you asked for. I am an idiot.
Attachment #565400 -
Attachment is obsolete: true
Attachment #567278 -
Flags: review?(dtownsend)
Assignee | ||
Comment 15•13 years ago
|
||
Oh, and I should say that my new patch was created with -w, for ease of reading.
Updated•13 years ago
|
Attachment #567278 -
Flags: review?(dtownsend) → review+
Updated•13 years ago
|
Keywords: dev-doc-needed
Assignee | ||
Comment 16•13 years ago
|
||
Assignee | ||
Updated•13 years ago
|
Keywords: checkin-needed
Comment 17•13 years ago
|
||
http://hg.mozilla.org/integration/mozilla-inbound/rev/5d9b31e32970
Keywords: checkin-needed
Target Milestone: --- → mozilla10
Comment 18•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/5d9b31e32970
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 19•13 years ago
|
||
Updated: https://developer.mozilla.org/en/Extensions/Bootstrapped_extensions#Adding_user_interface_with_a_chrome.manifest https://developer.mozilla.org/en/Firefox_10_for_developers
Keywords: dev-doc-needed → dev-doc-complete
You need to log in
before you can comment on or make changes to this bug.
Description
•