fix: normalize behavior of win.setOpacity() for invalid number values across operating systems
#19724
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
…es across operating systems
6 tasks
codebytere
reviewed
Aug 13, 2019
There was a problem hiding this comment.
@erickzhao 5-0-x doesn't use expect in that file: those tests all need to be assert-based, which is why CI is all failing.
codebytere
approved these changes
Aug 14, 2019
ckerr
approved these changes
Aug 15, 2019
|
Release Notes Persisted
|
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.
Backport of #19535.
See that PR for more details.
Notes: Normalized out-of-bound value behavior for the
setOpacity()API inBrowserWindow.