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

1.0.9.0 Cannot load all elements #159

Closed
Paethgoat opened this issue Jan 19, 2017 · 8 comments
Closed

1.0.9.0 Cannot load all elements #159

Paethgoat opened this issue Jan 19, 2017 · 8 comments
Assignees
Labels

Comments

@Paethgoat
Copy link

Paethgoat commented Jan 19, 2017

The update has now removed the controls for certain sites (https://teded.herokuapp.com/lessons/the-wars-that-inspired-game-of-thrones-alex-gendler as an example). You cannot enable the player, nor can you enable any elements for the page.

MSNBC.com is another example. Should it load it without the site being whitelisted, you are never given an option to whitelist and no elements can be enabled. This causes a scenario where it becomes impossible to view a site so long as ScriptSafe is running.

I've tried to upload a PNG screenshot and a JPEG screenshot, but I cannot attach it as the only message I receive is, "Something went really wrong, and we can’t process that file. "

Further testing shows this behavior is caused by the < NOSCRIPT > element being selected in "Disable and Remove."

@andryou
Copy link
Owner

andryou commented Jan 19, 2017

Thanks for the report; you may have done this but did you allow teded.herokuapp.com and teded.tedcn.com? (along with youtube.com and s.ytimg.com)

2017-01-19_17-34-50

Sometimes you need to allow the parent domain (e.g. teded.herokuapp.com) before the list of Blocked Items is populated (due to scripts being completely blocked and not loading external items).

@Paethgoat
Copy link
Author

Paethgoat commented Jan 19, 2017 via email

@andryou
Copy link
Owner

andryou commented Jan 19, 2017

Sorry I missed that part of your original post!

Could you please right-click in the panel, click on Inspect, and click on the "Console" tab and copy and paste any error messages into this issue?

2017-01-19 17_46_10

@Paethgoat
Copy link
Author

I am now unable to reproduce this bug. My apologies for the trouble.

@andryou
Copy link
Owner

andryou commented Jan 20, 2017

I'm glad that the issue is gone; thank you for being vigilant!

@andryou
Copy link
Owner

andryou commented Jan 22, 2017

I was able to reproduce this, reopening and will keep you updated. I hope to get a beta version for testing out this coming week. This is related to the option being enabled, as you've confirmed through your testing.

@andryou andryou reopened this Jan 22, 2017
@andryou andryou self-assigned this Jan 22, 2017
@andryou andryou added the bug label Jan 22, 2017
andryou added a commit that referenced this issue Jan 22, 2017
@andryou
Copy link
Owner

andryou commented Jan 23, 2017

v1.0.9.1 Beta is now available for testing: #166

@andryou
Copy link
Owner

andryou commented Jan 26, 2017

v1.0.9.1 has been published in the Chrome and Opera stores which addresses this issue. Thanks again for your report and testing!

@andryou andryou closed this as completed Jan 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants