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

Invalidate any content script #10

Merged
merged 1 commit into from
Feb 9, 2015
Merged

Invalidate any content script #10

merged 1 commit into from
Feb 9, 2015

Conversation

upsuper
Copy link
Contributor

@upsuper upsuper commented Feb 9, 2015

No description provided.

diafygi added a commit that referenced this pull request Feb 9, 2015
Invalidate any content script
@diafygi diafygi merged commit 938f862 into diafygi:master Feb 9, 2015
@ZimTester
Copy link

As I've already noticed, this fix doesn't bypass "match_about_blank": true in manifest.json anymore on newest versions of Chrome.

@upsuper
Copy link
Contributor Author

upsuper commented Feb 25, 2015

No, it still bypassed. The only difference is that, the new version of Chrome extends the range of sandbox, and not allowing scripts also disallows webrtc objects fetched from the iframe to be used.

@ZimTester
Copy link

@upsuper So what to do to bypass it on new version of Chrome? For me it's still blocked (clean installation with empty profile).
P.S. Sorry, fixed all my posts to include "newest versions of Chrome".

@upsuper
Copy link
Contributor Author

upsuper commented Feb 25, 2015

Yes, it fails to bypass the block now.

@upsuper
Copy link
Contributor Author

upsuper commented Feb 25, 2015

But interestingly, I still can, though a bit more compilcated.

Will submit a new patch soon.

@ZimTester
Copy link

@upsuper Thx, looking forward to it.

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

Successfully merging this pull request may close these issues.

3 participants