currentURL is not defined console error #267
Comments
|
Looks like this has popped up on stackoverflow too: |
|
We are also getting this error on all of our websites. When I turn Ghostery off, the error goes away. When I turn it back on, the error comes back so I have resorted to keeping Ghostery off until I need to see what tags are firing for QA purposes. |
|
I get this error consistently when I have Chrome Dev Tools opened during development. I get the message a brief moment after page load -- every time. FWIW in all cases the page I'm working on has a http://localhost:xxxx/xxxxxxx address. I haven't tried to debug the root cause yet, but it's definitely from the ghostery extension: |
|
It has been fixed in the development version. The error message should go away with the next release. |
|
@philipp-classen Thanks for fixing that! It breaks both Ghostery and some sites like Messenger in my Opera. Disabling Ghostery until the release fixes that. However, it's a strange feeling allowing all trackers in :( When do you expect the release, please? |
|
@iki Ghostery 8.3 is now in internal testing. From this point on, it is mostly about fixing regressions, but it depends on what issues will still be found. |
|
@iki Release is live. |

Description
currentURLis not defined in content_script_bundle.js on line 13.Expected Behavior
No console error.
Actual Behavior
Console error appears.

Steps to Reproduce
I've only noticed this on my website here, and it could be something to do with the Service Worker... Unfortunately I cannot get it to consistently occur, but I do know that it occurs on both my work computer and home computer (different computers, but same OS and browser).
When I was developing the service worker this error was happening often, but when only casually viewing the front-end it does not happen as often. If I can expectedly reproduce this I will certainly update this issue.
If I just load the site linked above and open the console and wait, it appears after a while (30-60s). I don't know if scrolling or clicking non-linked areas affect it.
Versions
The text was updated successfully, but these errors were encountered: