whitelist candidate lines #353
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
trevj
force-pushed
the
trevj-candidate-whitelist
branch
from
be9a5e6 to
cd20dec
Compare
trevj
force-pushed
the
trevj-candidate-whitelist
branch
from
cd20dec to
de0a663
Compare
|
Based on @bemasc's excellent diagnosis of the situation, BTW. |
|
👍 Beautiful |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduce a whitelist for candidate fields, the unexpected introduction of which has caused us some problems:
UWNetworksLab/uProxy-p2p#2167
Seems to fix the problem we've been seeing with Chrome 49+: