-
Notifications
You must be signed in to change notification settings - Fork 385
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
RegExp.prototype.flags cannot be read in Chrome Canary #370
Comments
That matches the spec. The error message summarizes it well. |
The problem is that our webapp breaks in es6-shim because it tries to test whether or not to shim the feature |
@fizker this is indeed part of the spec - you'll need to use |
@ljharb No, technically you need to use that :P. I have made a PR with it |
ha, touché. i haven't yet updated things to pass in Chrome Canary. Thanks for the PR. |
Fixed in c563abf |
Perfect :). Do you know when this will get released? I would prefer to get it into production as soon as possible, as the crash was rather nasty. |
I will release it shortly, but it's Chrome Canary - nobody using a canary build should have any expectation of any site working. Chrome Stable won't release with it for many weeks. |
Still, I would prefer having more time for testing, as we are not on the newest es6-shim. If I am not mistaken, we are still on a version that uses |
aha, that's a very very old version indeed - you will want to upgrade soon. I'll have v0.33.11 out today. |
Nice! Thanks :) |
One of the shims adds a getter for
RegExp.prototype.flags
, and guards against overriding the native by reading the current value.But reading
RegExp.prototype.flags
throws an error in Chrome Canary (48.0.2559.0):Uncaught TypeError: RegExp.prototype.global getter called on non-RegExp object
.Note: Chrome Canary requires the
Experimental JavaScript
flag to be enabled before exposingRegExp.prototype.flags
.The text was updated successfully, but these errors were encountered: