# Scripts not injected in Firefox 43.0

**URL:** <https://discourse.mozilla.org/t/scripts-not-injected-in-firefox-43-0/6121>\
**Category:** Development\
**Created:** [December 20, 2015, 10:45am UTC](https://discourse.mozilla.org/t/scripts-not-injected-in-firefox-43-0/6121 "2015-12-20T10:45:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![uri-wisestamp](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/uri-wisestamp/32/21435_2.png) [@uri-wisestamp](https://discourse.mozilla.org/u/uri-wisestamp)\
**Post date:** [December 20, 2015, 10:45am UTC](https://discourse.mozilla.org/t/scripts-not-injected-in-firefox-43-0/6121/1 "2015-12-20T10:45:48Z")

</div>

We created an extension for Firefox (we also have a Chrome version), which injects scripts into the page. Here is the code that injects the script in Firefox:

```
for (var i in tabs) {
	if (tabs[i].url.match(possible_urls) !== null) {
		tabs[i].attach({
			contentScriptFile: possible_urls_script_url
		});
	}
}

```

It worked until Firefox 42.0, but since version 43.0 it stopped working. I found [this document](https://blog.mozilla.org/addons/2015/11/19/compatibility-for-firefox-43/) and I think the first general item is related to us. But how do we make the script work?

In addition, we would like to check future versions of Chrome and Firefox with our extensions before they are released to the general public. How do we download and use them on Windows and Ubuntu?

`possible_urls_script_url` = “resource://example-at-example-dot-com/data/…/lib/content/src/common/first\_time\_script.js”

I also tried with “resource://example-at-example-dot-com/lib/content/src/common/first\_time\_script.js” and it doesn’t work either.

I found out that with Firefox Developer Edition (45.0a2) it works but with Firefox 43.0 it doesn’t.

Also when injecting with `contentScript` (instead of `contentScriptFile`) it still doesn’t work on Firefox 43.0. But it works on Firefox Developer Edition (45.0a2).

---

<div class="post-metadata">

**Author:** ![jorgev](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jorgev](https://discourse.mozilla.org/u/jorgev)\
**Post date:** [December 22, 2015, 10:25pm UTC](https://discourse.mozilla.org/t/scripts-not-injected-in-firefox-43-0/6121/2 "2015-12-22T22:25:57Z")

</div>

If your add-on is affected by the first bug in the blog post, then you’ll need to avoid injecting XUL/XBL content, or add a chrome.manifest file to your add-on marking the chrome domain with `contentaccessible=yes`.

> [@uri-wisestamp](#):
>
> In addition, we would like to check future versions of Chrome and Firefox with our extensions before they are released to the general public. How do we download and use them on Windows and Ubuntu

Not sure what you mean here. You can [get Beta and Developer Edition here](https://www.mozilla.org/en-US/firefox/channel/), and [Nightly here](http://nightly.mozilla.org/).

---

<div class="post-metadata">

**Author:** ![uri-wisestamp](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/uri-wisestamp/32/21435_2.png) [@uri-wisestamp](https://discourse.mozilla.org/u/uri-wisestamp)\
**Post date:** [December 23, 2015, 3:12pm UTC](https://discourse.mozilla.org/t/scripts-not-injected-in-firefox-43-0/6121/3 "2015-12-23T15:12:10Z")

</div>

Thank you. We released yesterday a new version without injecting the script and it’s waiting for Mozilla’s approval.