aboutsummaryrefslogtreecommitdiffstats
path: root/js/vapi-background.js
Commit message (Collapse)AuthorAgeFilesLines
* backportJesús2019-12-301-92/+20
| | | | | | - Flush caches on upgrade - Properly handle FrameModule's unloading - Use the new module and remove the old implementation
* remove tabs in javascript filesJesús2019-08-111-643/+643
|
* rebrand site URLJesús2019-08-101-3/+3
|
* Make components and Services.jsm globalAlessio Vanni2019-07-191-2/+0
| | | | Once again, but this time it works.
* Make vAPI definitely globalAlessio Vanni2019-07-041-2/+0
| | | | | At least for background.html, it can be defined once at the start of vapi-core and then populated.
* Revert "Make components and services global"Alessio Vanni2019-07-041-0/+2
| | | | | | This reverts commit 51f5e899fff9e804d9c91e4fefdd57ea5a85e99c. It seems to cause issues with the popup menu.
* Make components and services globalAlessio Vanni2019-07-041-2/+0
| | | | | Given that they are used a lot, at least in vAPI, let's just define/import them only once.
* Make vapi-cloud its own fileAlessio Vanni2019-07-041-128/+0
|
* Change how modules are importedAlessio Vanni2019-07-041-3/+2
| | | | | | | | 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.
* Temporarily fix undefined referenceAlessio Vanni2019-07-041-2/+2
| | | | | Ideally HttpObserver should be its own module, but right now it depends on too much "context" to be independent from vapi-background.
* Split context menu from vapi-backgroundAlessio Vanni2019-07-041-184/+0
| | | | Also fix a typo in Makefile.
* Get cookie management out of vapi-backgroundAlessio Vanni2019-06-231-101/+0
|
* Split vAPI.netAlessio Vanni2019-06-231-41/+0
|
* Make HTTPRequestHeaders a moduleAlessio Vanni2019-06-231-77/+3
| | | | The same as CallbackWrapper.
* Make CallbackWrapper a moduleAlessio Vanni2019-06-231-66/+0
| | | | | | In theory this way it can be used anywhere else if needed, but right now it's simply because it has to be placed somewhere and a module seems the best place for an object definition (constructor, etc.)
* Make messaging its own fileAlessio Vanni2019-06-231-108/+0
| | | | Also reorganize the Makefile a bit.
* Move storage APIAlessio Vanni2019-06-231-302/+0
| | | | | | Also remove optional cachestorage script. It doesn't exists and the cachedstorage, whatever it is, is defined as an alias for the normal storage system.
* Move browser-related entities away from vapi-backgroundAlessio Vanni2019-06-221-212/+0
|
* Move more entities to coreAlessio Vanni2019-06-221-31/+0
|
* Minor refactoringAlessio Vanni2019-06-221-1/+1
|
* Put window management into its own fileAlessio Vanni2019-06-221-238/+7
|
* Remove commented-out regionAlessio Vanni2019-06-221-132/+0
|
* More refactoringAlessio Vanni2019-06-221-11/+12
|
* Remove some cruftAlessio Vanni2019-06-221-1/+0
|
* Fix missing namespaceAlessio Vanni2019-06-211-1/+2
|
* Keep refactoringAlessio Vanni2019-06-211-19/+27
| | | | Exported stuff to handle the splitting.
* Make some private entities publicAlessio Vanni2019-06-211-24/+26
| | | | | Since things have been split, some of these have to be exposed to the rest of the world.
* Split tab handling from vapi-backgroundAlessio Vanni2019-06-211-704/+8
| | | | That file is too large, let's split it up.
* Don't use child-srcAlessio Vanni2019-06-191-1/+4
| | | | | | | It generates an error in the browser console and it's rather annoying. There is still one error being generated, but it's unclear from where it comes from. Not yet tested in Basilisk.
* Fix typos and reinstate some old declarationsAlessio Vanni2019-06-191-11/+11
|
* Reformat style (huge and mostly boring commit)Alessio Vanni2019-06-191-3144/+3175
|
* Another fixAlessio Vanni2019-05-171-1/+1
|
* Fix migration againAlessio Vanni2019-05-171-2/+3
|
* Fix migration from old pathAlessio Vanni2019-05-171-1/+2
| | | | | | uBlock Origin also uses "extension-data" as a directory, so moving the whole thing is a bad move. Instead, simply move the ematrix.sqlite database from one place to another.
* Remove a debugging statementAlessio Vanni2019-05-131-1/+0
|
* Fix handling of existing dataAlessio Vanni2019-05-131-2/+1
|
* Fix typoAlessio Vanni2019-05-121-1/+1
|
* Migrate database from old directoryAlessio Vanni2019-05-121-1/+9
|
* Change directory name to be more informativeAlessio Vanni2019-05-121-1/+1
|
* Use "modern" branch unconditionallyAlessio Vanni2019-04-231-6/+9
| | | | | | | Tests showed that it works without any noticeable problems. As such, it was deemed better to throw it in the wild and see what happens. If there are any problems, this commit can simply be reverted.
* Use the right property for version checks in BasiliskAlessio Vanni2019-03-141-5/+2
|
* Let Basilisk be considered "modern Firefox"Alessio Vanni2019-03-141-2/+3
|
* Remove useless preference and check app ID in second Basilisk branchAlessio Vanni2019-03-111-6/+6
| | | | | | | | the `forceLegacyToolbarButton' preference is useless because on Pale Moon the button is always added with the "legacy" method, while on Basilisk it's always added with CustomizableUI, so there is nothing to "force" here. Also add a check that was forgotten in the previous commit.
* Check how to add the button based on the app IDAlessio Vanni2019-03-111-15/+14
| | | | | | | Unlike checking different versions of Firefox, the features that Basilisk has over Pale Moon (and viceversa) are better known and just checking the application ID is enough to understand how to add the button to the toolbar.
* Improve space elements detectionAlessio Vanni2019-03-041-5/+21
|
* Improve the double tooltip fixAlessio Vanni2019-02-271-0/+3
| | | | | | This way, the toolbar button can display its tooltip, making it coherent with other toolbar buttons, without covering the popup panel tooltips.
* Recover tooltip text for BasiliskAlessio Vanni2019-02-271-1/+4
| | | | | It appears that with CustomizableUI, the double tooltip issue is not present. Thus, the tooltip can be safely used.
* Let the toolbar button honor spacers in toolbarAlessio Vanni2019-02-271-1/+8
|
* Remove double tooltipAlessio Vanni2019-02-221-2/+0
| | | | | Previously, the XUL tooltip would hide part of the second tooltip, generated by the buttons inside the popup.
* Reinstate options.xulAlessio Vanni2019-02-201-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-07 19:46:44 +0000