-
-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
should not working in browser #6
Comments
this is in Firefox 9.0.1 |
The should interface does it's thing by extending Unfortunately, nothing can be done. My recommendation is to use the
All of the same language applies. |
Very odd. This seems to work fine in firefox:
What, specifically, does firefox not like? It seems like it's fine with extending the Object.prototype, but all strings, numbers, etc, turn into object literals inside the property? is that right? |
Found a bit of a work around. Check out branch bug/issue-6 ... 067d966 Should tests for this branch are passing in Chrome 16, FF 9.0.1, Safari 5.1.2. Let me know if it works out and I will pull it into the next release later today/tomorrow. |
I just grabbed 0.1.7 and everything works great in firefox now. Thanks! |
This patch has been included in 0.1.7. The commit was 48f3815 if your curious. I also retract my previous statement. Apparently something can be done. Thanks for the motivation :) Let me know if it troubles you further. |
FYI, it's really close to working in IE9 as well. For some reason any number sets this == 0. Trying to figure out a workaround. Other than that, everything seems to work |
That would be awesome if it did. Thanks for the update... will accept pull requests! |
Should the website be updated? It still says "Should tests do not run in the browser." |
Yeah, the api also a few versions outdate. I'm in the process of updating my docs generator so should be up in a day or two. Opened #12 in response. |
In firebug:
The text was updated successfully, but these errors were encountered: