Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

Webextension run_at in manifest.json not working correctly

  • 1 amsa
  • 2 sa na da wannan matsala
  • 2 views
  • Amsa ta ƙarshe daga Paul

more options

You can define to load a page at a certain time of building DOM using run_at: for example with parameter page_start. this isn't working either. it seems to me that either the script is being run asynchronous, or there is some other reason for this not to be working: aall=document.getElementsByTagName("*"); for (var i=0, max=aall.length; i < max; i++) { aall.addEventListener=function(a,b,c){ console.log("Log"); return false; }; } console.log("Log"); is never being called, even though an event has been added to the element using addEventListener. My current solution for this is an own firefox fork that overwrites the functions in the javascript engine, which is kind of overdosed.

You can define to load a page at a certain time of building DOM using run_at: for example with parameter page_start. this isn't working either. it seems to me that either the script is being run asynchronous, or there is some other reason for this not to be working: aall=document.getElementsByTagName("*"); for (var i=0, max=aall.length; i < max; i++) { aall.addEventListener=function(a,b,c){ console.log("Log"); return false; }; } console.log("Log"); is never being called, even though an event has been added to the element using addEventListener. My current solution for this is an own firefox fork that overwrites the functions in the javascript engine, which is kind of overdosed.

Mafitar da aka zaɓa

Hi

if you have a question about add-on development, I recommend you ask in the main add-on forums at https://discourse.mozilla.org/c/add-ons.

Karanta wannan amsa a matsayinta 👍 0

All Replies (1)

more options

Zaɓi Mafita

Hi

if you have a question about add-on development, I recommend you ask in the main add-on forums at https://discourse.mozilla.org/c/add-ons.