Skip to content

Chrome error: "Denying load of" #128

dy-dx opened this Issue Jul 25, 2013 · 25 comments
dy-dx commented Jul 25, 2013

Chrome Version 29.0.1547.32 beta

I am getting this error in the javascript console on every page I visit:

Denying load of chrome-extension://jeoacafpbcihiomhlakheieifhpjdfeo/scripts/vendor/jquery/
Resources must be listed in the web_accessible_resources manifest key in order to be loaded by pages outside the extension.
dy-dx commented Jul 26, 2013

This appears to be an issue with chrome 29 and source maps (line 4 of .../vendor/jquery/jquery.js). Unchecking "Enable source maps" in DevTools stops the error. Closing...thanks

@dy-dx dy-dx closed this Jul 26, 2013

Cool, thanks for the heads-up!

massar commented Aug 12, 2013

To resolve this error, which is IN, just remove the reference from jquery.js (aka the end of the last line):

diff --git a/firefox/content/disconnect.safariextension/opera/chrome/scripts/vendor/jquery/jquery.js b/firefox/content/disconnect.safariextension/opera/chrome/scripts/vendor/jquery/jquery.js
index 50d1b22..b265e96 100644
--- a/firefox/content/disconnect.safariextension/opera/chrome/scripts/vendor/jquery/jquery.js
+++ b/firefox/content/disconnect.safariextension/opera/chrome/scripts/vendor/jquery/jquery.js
@@ -1,4 +1,4 @@
 /*! jQuery v1.9.0 | (c) 2005, 2012 jQuery Foundation, Inc. | */(function(e,t){"use strict";function n(e){var t=e.length,n=st.type(e);return st.isWindow(e)?!1:1===e.nodeType&&t?!0:"array"===n||"function"!==n&&(0===t||"number"==typeof t&&t>0&&t-1 in e)}function r(e){var t=Tt[e]={};return st.each(e.match(lt)||[],function(
 },set:function(e,n,r){return st.nodeName(e,"input")?(e.defaultValue=n,t):Ct&&Ct.set(e,n,r)}}),Ht||(Ct=st.valHooks.button={get:function(e,n){var r=e.getAttributeNode(n);return r&&("id"===n||"name"===n||"coords"===n?""!==r.value:r.specified)?r.value:t},set:function(e,n,r){var i=e.getAttributeNode(r);return i||e.setAttributeNode(i=e.ownerDo
 },nextAll:function(e){return st.dir(e,"nextSibling")},prevAll:function(e){return st.dir(e,"previousSibling")},nextUntil:function(e,t,n){return st.dir(e,"nextSibling",n)},prevUntil:function(e,t,n){return st.dir(e,"previousSibling",n)},siblings:function(e){return st.sibling((e.parentNode||{}).firstChild,e)},children:function(e){return st.s
\ No newline at end of file

Reopening and reassigning to consider @massar's comment (thank you).

@carbureted carbureted was assigned Aug 12, 2013
mdeeter commented Aug 12, 2013

I had this same problem on a plugin of my own.

I ended up downloading the .map file and added it to my manifest to solve.

"web_accessible_resources": [

Here's where I got the .map file:


Ah, I see. Thanks a lot everybody for all the helpful info!

@oldestlivingboy oldestlivingboy added a commit that closed this issue Aug 20, 2013
@oldestlivingboy oldestlivingboy Closed #128. 549f862
mdeeter commented Aug 20, 2013

Just curious, is an update coming to fix this... is that why it was closed?

Zegnat commented Aug 20, 2013

@mdeeter, yes. If you check the change made by commit 549f862 you will see @byoogle took away this line from jQuery:


Without this line the browsers will no longer try to use the .map file. This is a slightly more elegant solution than adding the file to the add-on like you proposed before.


Note: The fix isn't in the production version yet. I'm working with a couple users to (hopefully) fix one more bug (#133) then will do a new release. (There should really be a way to say when the code has gone to production.)

Zegnat commented Aug 20, 2013

(There should really be a way to say when the code has gone to production.)

I believe most people use tags for that. They just tag the commits that mark a new release. Maybe something you could start doing?


Cool, thanks, will do!


@Zegnat Did I do the tagging right? (The results are less dramatic than I had expected.)

Zegnat commented Aug 22, 2013

Looks right, now a ‘release’ menu item is showing on the Disconnect GitHub page and anyone going there can click on 5.7.1 to see the code for that release.

It’s really not about dramatic results. On GitHub (or any other versioning system) the development of software is linear and every commit marks a new release. This is just not true for how software is normally released. Using tags pretty much allows you to say ‘this commit marks a new public release’.

Some people like it, some don’t, you’ll have to experiment with it and see how it works for you. It is a good way to make it clear at what point during all your commits you release a new stable release.


It goes a bit deeper than just stating "this commit markt a public release"; it allows for systems to state dependencies on other projects by version and stability.. your tags may allow for v1.5.0-beta for example, or v1.5.0-rc1 etc..

Versioning is usually done by Semantic Versioning logic,


Thank you for the pointers!

@mjb2010 mjb2010 referenced this issue in disconnectme/chrollusion Nov 4, 2013

Resource not accessible in chrome #28


Denying load of chrome-extension://jeoacafpbcihiomhlakheieifhpjdfeo/scripts/vendor/jquery/ Resources must be listed in the web_accessible_resources manifest key in order to be loaded by pages outside the extension.

I'm still getting this particular error, just wondering if the fix was already released or is it yet to be?


The fix was released in v5.7.1. I think there was a regression because of changes in Chrome 31, so the error has been re-fixed in v5.10.2 (which was just pushed).


👍 thanks, I just updated manually to 5.10.2 and it works fine!

tim66 commented Apr 11, 2014

It seems the bug again appeared.
Chromium 34; x86_64 GNU/Linux.

@ptariche ptariche referenced this issue in scdoshi/jquery-ajaxchimp Jun 11, 2014

mailchimp ajax submit error: parsererror #18

jvthert commented Sep 5, 2014

This bug is alive and kicking. Removing the reference to the map file from jQuery solves it.
I'm on safari 7.0.6 on Mavericks. But this is unrelated to the browser version.


And I do find that connecting to https://localhost:3131 and accepting it is required before the dotscripts start running smoothly.


Just in case anyone is still getting this error - I found Kaspersky Virtual Keyboard extension seemed to be causing the error (part of Kaspersky Virus checking install) - as soon as I disabled it the error disappeared.

Lecss commented Dec 21, 2014

In my case, removing the Collusion extension on chrome fixed the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.