-
Notifications
You must be signed in to change notification settings - Fork 32
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
Potential edge case bugs #13
Comments
Yeah I saw that gist, very useful. I looked at the string trim issue, I decided not to include that in this release because I want to do a bit more testing around it. Checking in chrome the native implementation seems to fail on some of those whitespace like characters, which is confusing because according to Kangax's article seems to imply that chrome shouldn't fail. I'll spend some more time looking into this though as I would like augment to be close to agree with the spec where possible/reasonable. |
For what its worth this is the test (adapted from es5-shim) that I had that failed in chrome:
|
Interesting. Can't trust those browsers :(. Good job on the whole making it spec compliant thing though o/ |
I think I remember seeing Chrome fail test-262 tests for whitespace in |
https://gist.github.com/1120592
Lists a bunch of bugs that are in various implementations of ES5 shims. You may want to thoroughly check yours does not fail any.
For example
Note that
\s
fails in IE sometimes (because IE, rage.)The text was updated successfully, but these errors were encountered: