Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Webextension run_at in manifest.json not working correctly

  • 1 réponse
  • 2 ont ce problème
  • 6 vues
  • Dernière réponse par 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.

Solution choisie

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.

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (1)

more options

Solution choisie

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.