On Dec 6, 2010, at 5:34 AM, Patrick Mueller wrote:
> There was an attempt to fix this, in this WebKit bug:
>
>https://bugs.webkit.org/show_bug.cgi?id=32722
>
> It's a JSC issue. I'm not clear what the current status is of the JSC parser.
How is it not clear? That bug is marked resolved as
There was an attempt to fix this, in this WebKit bug:
https://bugs.webkit.org/show_bug.cgi?id=32722
It's a JSC issue. I'm not clear what the current status is of the JSC
parser.
On Mon, Dec 6, 2010 at 06:08, Jeremy Orlow wrote:
> I'm pretty sure this was discussed and that EMCA5 does make
Should the spec have notes referring to the fact that it requires ECMA5
conformance or parse errors may result?
I'm bringing this up regarding backward compatibility, as reserved
words, if not escaped, lead to parse errors.
Somewhat useful table:
http://kangax.github.com/es5-compat-table/
It
This should work fine in a nightly already, if it doesn't you need to file a
bug.
--Oliver
On Dec 6, 2010, at 3:08 AM, Jeremy Orlow wrote:
> I'm pretty sure this was discussed and that EMCA5 does make it possible to
> use continue as we do. At least that's the conclusion we had with delete.
I'm pretty sure this was discussed and that EMCA5 does make it possible to
use continue as we do. At least that's the conclusion we had with delete.
My guess is that the JavaScriptCore (WebKit's main JavaScript engine)
parser needs to be changed. If so, you should probably file a bug at
webkit.o
I just noticed that the cursor "continue" method in IndexedDB runs afoul
of the Safari js parser, with "continue" being a reserved word.
Was there any discussion on this issue? Should there be? Should I not
worry about it, and use cursor['continue'] instead of cursor.continue() ?
-Charles
