| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
- Flush caches on upgrade
- Properly handle FrameModule's unloading
- Use the new module and remove the old implementation
|
| |
|
| |
|
|
|
|
| |
Once again, but this time it works.
|
| |
|
|
|
|
|
| |
At least for background.html, it can be defined once at the start of
vapi-core and then populated.
|
|
|
|
|
|
| |
This reverts commit 51f5e899fff9e804d9c91e4fefdd57ea5a85e99c.
It seems to cause issues with the popup menu.
|
|
|
|
|
| |
Given that they are used a lot, at least in vAPI, let's just
define/import them only once.
|
|
|
|
|
|
|
|
| |
I can't really find a reason why the returned value is preferred over
the normal importing process.
Additionally, there's a good chance importing Services.jsm can be done
only once at the start of everything, instead of binding each object
to a separate closure.
|
|
|
|
|
|
| |
While they are technically informative, the splitting makes things
easier to follow already (somewhat) and there's not really a need to
list each global variable (there aren't many anyway.)
|
| |
|
|
|