-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Usage shortcuts of arguments object breaks old version of WebKit #150
Comments
Interesting. It means this code doesn't work in this WebKit version: (function(){
var $$ = arguments;
return $$[0];
})(42); Can you confirm it? |
That doesn't appear to cause it. I also tried (function(){ var $$ = arguments, $$len = $$.length, i = 0; while(i<$$len){ $$[i]; i++; } })(42, 43) and that didn't cause it either. If I |
I have no ideas what else can cause this problem. Can you add some additional info - version, line, stack, etc? |
As I mentioned in chat, I can't get much more info. Here is the line causing it: const props = {
...this.props,
href: path + wrappedWindow.location.search,
onClick(e) {
e.preventDefault()
navigationActions.changePath(path)
},
} It is in a react component that is rendered several times on a page. It's only the last call to it that has the problem, all the others are fine. |
It happens after maybe 80 calls to it, so it's very likely a broken optimization |
Great, thanks. Any chance of a 1.2.7 w/ this applied? |
It's not a critical bug (a very specific engine), so I don't think makes sense publish |
Ok, thanks. I don't think I can use 2.0 yet because too many things are pinned to 1.0 but I forked it, so it's ok. Thanks! |
Fixed in 2.0. |
Ok, this is an odd one and is more likely a (fixed) webkit issue and not a core-js issue, but I wanted to point it out here in case you wanted to do something about it.
This change: 5bcabca#diff-f68e573b7ecfc93a7afcce675b0459eaL24
Causes this error:
On this stack in capybara-webkit:
But it works fine on OS X with a newer version of Qt:
The text was updated successfully, but these errors were encountered: