Stop accessing missing properties of Document #127
Conversation
This file contains hidden or 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
This fixes the script on IE. Apparently, according to the WebIDL standard, you should not be able to access these properties, even to check if they exist, and so IE keeps you from doing it. It's arguable if the standard means anything if IE is the only browser to follow it, but that's the web for you. A simple workaround is to ask hasOwnProperty(); alas, this defeats some of the prettiness of the coffeescript. Its only advantage is that it is functional.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This fixes the script on IE. Apparently, according to the WebIDL standard, you should not be able to access these properties, even to check if they exist, and so IE keeps you from doing it. It's arguable if the standard means anything if IE is the only browser to follow it, but that's the web for you.
A simple workaround is to ask hasOwnProperty(); alas, this defeats some of the prettiness of the coffeescript. Its only advantage is that it is functional.