Work-around to avoid "Unsafe JavaScript attempt to access frame" warning #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Using gulp-qunit 1.0.0 with PhantomJS 1.9.12, following warning is output.
This is a issue of PhantomJS. Please see: ariya/phantomjs#12697
Change
I add work-around to avoid "Unsafe JavaScript attempt to access frame" warning.
Tests
We can confirm that "Unsafe JavaScript attempt to access frame" warning is avoided by this change:
(I think test is not needed, so this change was not committed.)
Thanks.