Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

currentURL is not defined console error #267

Closed
chrisblakley opened this issue Dec 9, 2018 · 7 comments
Closed

currentURL is not defined console error #267

chrisblakley opened this issue Dec 9, 2018 · 7 comments
Assignees

Comments

@chrisblakley
Copy link

@chrisblakley chrisblakley commented Dec 9, 2018

Description

currentURL is not defined in content_script_bundle.js on line 13.

Expected Behavior

No console error.

Actual Behavior

Console error appears.
screen shot 2018-12-08 at 11 24 14 pm

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

  • Browser: Chrome 71.0.3578.80
  • OS: Mac Os 10.14.1

screen shot 2018-12-08 at 11 36 05 pm

@clt2rdu
Copy link

@clt2rdu clt2rdu commented Dec 13, 2018

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.

@bseib
Copy link

@bseib bseib commented Jan 1, 2019

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:

image

@philipp-classen
Copy link
Contributor

@philipp-classen philipp-classen commented Jan 3, 2019

It has been fixed in the development version. The error message should go away with the next release.

@iki
Copy link

@iki iki commented Jan 6, 2019

@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?

@philipp-classen
Copy link
Contributor

@philipp-classen philipp-classen commented Jan 6, 2019

@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.

@philipp-classen
Copy link
Contributor

@philipp-classen philipp-classen commented Jan 16, 2019

@iki Release is live.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants