Skip to content
Advertisement

Tag: firefox-addon

Does loading a webextension’s background.js script impact performance, even if the script’s contents are minimal?

When installing a webextension, does the mere existence of a background.js file negatively impact performance* at all, considering that it is a separate javascript file that must be loaded? For most practical cases one could assume the answer is “pretty much No,” but in the case of an older computer with less processing power, and a browser that could have

BlockingResponse in Firefox extension

I’m attempting to redirect a user in a Firefox extension like so: I’ve added webRequest and webRequestBlocking permissions in the manifest. In the debugger, I see that I am reaching the return statement with the redirectUrl correctly set, but the webpage does not redirect. I would assume this should redirect based upon the webRequest documentation, however the temporary extension does

page_action click does not work while browser_action click works in Chrome Extension?

I want to make a simple browser extension like Font Face Ninja which toggles UI when page_action or browser_action is clicked. The following code using browser_action works – background.js manifest.json While the following code using page_action does not work – background.js manifest.json According to MDN docs, Page actions are like browser actions, except that they are associated with particular web

Bootstrap addon create options button with arbitrary js

I figured out from Bugzilla that you can set your options url in install.rdf to arbitrary js and it will run perfectly fine. The only issue is that the window deactivates, its as if an invisible dialog has opened over it, and no matter what you can’t close it. For example: In my addon here: simple test case, on startup

How to get notified about changes of the history via history.pushState?

So now that HTML5 introduces history.pushState to change the browsers history, websites start using this in combination with Ajax instead of changing the fragment identifier of the URL. Sadly that means that those calls cannot be detect anymore by onhashchange. My question is: Is there a reliable way (hack? ;)) to detect when a website uses history.pushState? The specification does

On Text Highlight Event?

I’m curious if anyone knows how I would trigger a function to run if/once the user finishes selecting text on the web page? I would like the user to be able to select text, and after a short delay(or immediately, at this point it doesn’t matter much) an overlay button appears near the text that the user can then click

Advertisement