Bug 23097 - Why does WebKit run into JavaScript1.7 blocks without supporting any feature of JavaScript 1.7
: Why does WebKit run into JavaScript1.7 blocks without supporting any feature ...
Status: UNCONFIRMED
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore
: 528+ (Nightly build)
: Macintosh Mac OS X 10.5
: P3 Normal
Assigned To: Nobody
https://developer.mozilla.org/en/New_...
: NeedsRadar, NeedsReduction, ReviewedForRadar
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-04 06:18 PST by Georg Maaß
Modified: 2012-05-30 14:51 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Georg Maaß 2009-01-04 06:18:06 PST
Why does WebKit run into JavaScript1.7 blocks without supporting any feature of JavaScript 1.7. From the results of my tests, I confirm Safari 3.2 supporting JavaScript 1.6, but testing those language features that make the difference between 1.6 and 1.7 WebKit 528+ fails in each test case. It neither supports block scope variables using the new keyword let nor does it support generators using the new keyword yield nor does it support de structuring assignments.

Without implementing these language features, it should not run into javascripts with language="javascript1.7" or type="application/javascript;version=1.7" because those scripts usually make use of exactly those language features not yet implemented in WebKit.
Comment 1 Julien Chaffraix 2012-05-29 11:44:20 PDT
CC'ing some (I hope relevant) people.
Comment 2 Adam Barth 2012-05-29 16:32:06 PDT
This area is a bit of a mess.  My understanding is that TC39 has abandoned out-of-band versioning for JavaScript.  We execute whatever types the HTML5 spec tells us to execute.
Comment 3 Alexey Proskuryakov 2012-05-30 14:51:40 PDT
See also: bug 87527.