-
Notifications
You must be signed in to change notification settings - Fork 19
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
Issue: Website layout is broken in Chrome by this extension #165
Comments
I'm not sure if this is a language error (maybe it runs on sites not in English?). Normally, there would be an
|
The unexpected token error Assuming error is in |
Hi @PotatoQuality, could you take a look at my comment? |
Hi @Ephellon, issues as being fixed after reinstalling the plugin. Thanks for your quick help <3 |
Not sure how this keeps happening... |
Notes to self:
|
Originally posted by @sp00kie in #168.605748176 It seems |
Possibly remote styling, though it still doesn't recreate the problem for me... |
Fixed. Problem was in |
Reopening so that I can pin the issue for other users to see |
All websites are broken unless i uninstall or don't allow addin to access that website. Why does it need access to all websites anyway? it should only need the ones it works with. I really liked the old 3.4 version, so much simpler. |
FAQs — Why does the extension want access to all sites?
|
Still really crazy without that dev mode. (you wrote about it only here: webtoplex#5 (comment) ; it should probably be on by default while this version is so unstable) |
If experiencing this issue still, please do the following →
Describe the error
Its look like sites that aren't the Web to Plex website getting broken by the last version of this plugin. if a unstall the plugin everything is fine.Edit: It looks like sites that aren't Web to Plex are broken by the latest version. If I uninstall the extension, everything works fine.
To Reproduce
Estimated location
Uncaught SyntaxError: Unexpected token '<' VM72:18
0P
Screenshots
Extension Information
4.1.2.4
store
chrome
The text was updated successfully, but these errors were encountered: