Status: New
Owner: ----
New issue 2917 by [email protected]: Parser doesn't work well when
keywords are used as parameter names
http://code.google.com/p/v8/issues/detail?id=2917
With the introduction of JS 1.7 support in v8 I noticed that if a keywork
is used as a parameter name for a function it will break the parser but
doesn't do such on Firefox.
JSFiddle example: http://jsfiddle.net/YvMsp/2/
Result in Firefox 24.0: Alert window pops up
Result in Chrome 29: Parser throws an error "Uncaught SyntaxError:
Unexpected token let"
I'm running on Arch Linux x64 kernel 3.11.2 and I have "Experimental
Javascript" flag enabled in the chrome://flags section. The "Experimental
Javascript" flag is required to replicate the bug.
I can verify the issue can be observed on Windows 7 x64 as well.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
