fix coffeecup in the browser #31
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
twilson63
pushed a commit
that referenced
this pull request
May 26, 2012
fix coffeecup in the browser
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.
I ran into two issues using coffeecup.js in the browser:
first: IE8 improperly rendered ids when using the shortcut syntax, so
rendered
(this was an existing bug in CoffeeKup... I think it's actually an improper use of CoffeeScript -- it doesn't strings guarantee String to be enumerable). This closes issue #12.
second: requiring stylus was done without a guard to ensure we're in the node enviroment (or at least one that knows what "require('stylus')" means). This change might be shortsighted -- open to feedback if it is.
--Bob