[dom] Normalize setting a node value to null #1611
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
When set a node value to `null`, then a node value returns `"null"` as string on the legacy IE (IE <= 9). A node value returns an empty string on the modern browsers (Chrome, Firefox, IE >= 10). This change is to normalize the results of setting a node value to `null` on any browsers. Fix yui#1603.
|
👍 Thanks. |
|
Merged. @ezequiel Thanks for your review! |
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.
When set a node value to
null, then a node value returns"null"as string on the legacy IE (IE <= 9). A node value returns an empty string on the modern browsers (Chrome, Firefox, IE >= 10). This change is to normalize the results of setting a node value tonullon any browsers. Fix #1603.Tested with IE6, IE7, IE8, IE9, IE10, IE11, Chrome, Firefox, Safari 7(OS X), Safari 7(iOS).