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!

Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Webextension run_at in manifest.json not working correctly

  • 1 Mbohovái
  • 2 oguereko ko apañuãi
  • 2 Hecha
  • Mbohovái ipaháva 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.

Ñemoĩporã poravopyre

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.

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 0

Opaite Mbohovái (1)

more options

Ñemoĩporã poravopyre

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.