This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Expand "use strict" use & drop (broken) old Opera mixedcontent support #3961
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.
I found this fun bug while expanding "use strict" for some ES6 features:
Because of the IIFE (immediately-invoked function expression) surrounding
localPlatformRegexp, it's never worked.this.userAgentis undefined during execution, and the else is always taken, resulting inchromiumbeing the platform -- always.Let's just rip this out, since it hasn't worked and
mixedcontentsupport has been dead for a while in Chrome (and FF 23+, and Opera 23+).In the future, we should consider allowing Chrome users to enable
mixedcontentrules, similar to the FF behavior.Signed-off-by: Nick Semenkovich [email protected]