JS 1.7 support: Who has it, etc.?

Which browsers, if any, other than FF2/3, support Javascript 1.7? And
in those, how do you turn it on? As in, for FF2 you must say:

<script type="application/javascript;version=1.7">

or the equivalent. Do you know the timeline for upcoming JS 1.7
support in browsers that don't currently support it?

joebloe wrote:

Which browsers, if any, other than FF2/3, support Javascript 1.7?

Other Mozilla browsers like SeaMonkey or Camino do. Actually I know that
SeaMonkey does, I have never used Camino but it is based on Gecko and
Spidermonkey as well so I would be pretty suprised if the latest Camino
version would not support JavaScript 1.7.


--

Martin Honnen
http://JavaScript.FAQTs.com/

Maybe I am not looking in the right place, but it has seemed bizarrely
difficult to determine what browser supports what, and what an
upcoming release will support. Mozilla's developer page says, plainly,
"Version xx supports 1.6 and here are the new features in 1.6 and how
to use them ... Version xx supports 1.7 and here are ..." etc. But
where is that for MSIE, Opera, Safari, ....?

The application I'm working on doesn't have to be backward compatible
with anything and I'm even okay with requiring a user to run it from
FF2 or FF3, but I'd like to know what's up with the rest of the
browser world where future JS/ECMAscript support is concerned.

On May 16, 10:41 am, Martin Honnen <mahotr... (AT) yahoo (DOT) de> wrote:

joebloe wrote:
Which browsers, if any, other than FF2/3, support Javascript 1.7?

Other Mozilla browsers like SeaMonkey or Camino do. Actually I know that
SeaMonkey does, I have never used Camino but it is based on Gecko and
Spidermonkey as well so I would be pretty suprised if the latest Camino
version would not support JavaScript 1.7.

joebloe wrote:

Maybe I am not looking in the right place, but it has seemed bizarrely
difficult to determine what browser supports what, and what an
upcoming release will support. Mozilla's developer page says, plainly,
"Version xx supports 1.6 and here are the new features in 1.6 and how
to use them ... Version xx supports 1.7 and here are ..." etc. But
where is that for MSIE, Opera, Safari, ....?

The application I'm working on doesn't have to be backward compatible
with anything and I'm even okay with requiring a user to run it from
FF2 or FF3, but I'd like to know what's up with the rest of the
browser world where future JS/ECMAscript support is concerned.

Wikipedia has a comparison table. I can't vouch for its accuracy, but
it seems like it's better than nothing:

http://en.wikipedia.org/wiki/Compari...8ECMAScript%29

Jeremy

On May 16, 12:23 pm, Jeremy <jer... (AT) pinacol (DOT) com> wrote:

Wikipedia has a comparison table. I can't vouch for its accuracy, but
it seems like it's better than nothing:

http://en.wikipedia.org/wiki/Compari...es_%28ECMAScri...

I saw that, but I don't know where they got that info from, and on its
surface it is wildly inaccurate. :-(

On Fri, 16 May 2008 at 10:47:27, in comp.lang.javascript, joebloe wrote:

Maybe I am not looking in the right place, but it has seemed bizarrely
difficult to determine what browser supports what, and what an
upcoming release will support. Mozilla's developer page says, plainly,
"Version xx supports 1.6 and here are the new features in 1.6 and how
to use them ... Version xx supports 1.7 and here are ..." etc. But
where is that for MSIE, Opera, Safari, ....?
snip

Microsoft has never been good at saying what it's done. There are legal
reasons why it has to be very careful about announcing what future
products will do.

Where does the number 1.7 come from ?

John
--
John Harris

On May 16, 9:47 pm, joebloe <remid0d... (AT) gmail (DOT) com> wrote:

Maybe I am not looking in the right place, but it has seemed bizarrely
difficult to determine what browser supports what, and what an
upcoming release will support. Mozilla's developer page says, plainly,
"Version xx supports 1.6 and here are the new features in 1.6 and how
to use them ... Version xx supports 1.7 and here are ..." etc. But
where is that for MSIE, Opera, Safari, ....?

Microsoft has its own brand name of ECMAScript implementation called
JScript and its own version numbering schema going from IE3 (the first
one with JScript support). The schema is not fully consistent, being
attached at different times either to major JScript update or to the
browser version number. See it at:
http://msdn.microsoft.com/en-us/libr...9e(VS.80).aspx
See also version vector details for conditional comments at
http://msdn.microsoft.com/en-us/libr...9e(VS.80).aspx
The current version for both IE6 and IE7 it is 5.6 with lesser-major
numbers different. On any IE just run
window.alert(''.concat(
ScriptEngineMajorVersion(), '.',
ScriptEngineMinorVersion(), '.',
ScriptEngineBuildVersion()
));
to see the exact numbers.
There is a gap left between 5.6 and 7 for upcoming upgrades, and the
next version number in use is 7.0 for JScript.NET but this engine is
server-side only so out of your interest I guess.

Other producers are using the original Netscape numbering schema with
JavaScript 1.0 for Netscape 2.x and JavaScript 1.5 being the current
industry standard de facto.
JavaScript 1.5 is pretty much equal to JScript 5.6 lesser some minor
algorithm implementations.

JavaScript 1.6 (Firefox 1.5) and JavaScript 1.7 (Firefox 2.0) are
Mozilla Foundation proprietary extensions of the base 1.5
Not all feature are backward compatible with 1.5, but any 1.5-
compliant program will run under 1.6 or 1.7

So overall you don't need to have any headache at all with versions
unless you want to use some of new Gecko-specific features.

Hope it helps.

On May 18, 12:46 pm, VK <schools_r... (AT) yahoo (DOT) com> wrote:

JavaScript 1.6 (Firefox 1.5) and JavaScript 1.7 (Firefox 2.0) are
Mozilla Foundation proprietary extensions of the base 1.5
Not all feature are backward compatible with 1.5, but any 1.5-
compliant program will run under 1.6 or 1.7

So overall you don't need to have any headache at all with versions
unless you want to use some of new Gecko-specific features.

Hope it helps.

Well, I'm committed to using JS 1.7 features (like let :-) so I guess
it'll be Gecko for me for at least another year. Or four. Which is
okay; I have no problem telling people to use Firefox for my (game)
application. But who knows, maybe Webkit will implement 1.7/1.8/etc.
before then. Opera and MSIE, forget it....

-j

On May 19, 9:38 pm, joebloe <remid0d... (AT) gmail (DOT) com> wrote:

On May 18, 12:46 pm, VK <schools_r... (AT) yahoo (DOT) com> wrote:

JavaScript 1.6 (Firefox 1.5) and JavaScript 1.7 (Firefox 2.0) are
Mozilla Foundation proprietary extensions of the base 1.5
Not all feature are backward compatible with 1.5, but any 1.5-
compliant program will run under 1.6 or 1.7

So overall you don't need to have any headache at all with versions
unless you want to use some of new Gecko-specific features.

Hope it helps.

Well, I'm committed to using JS 1.7 features (like let :-) so I guess
it'll be Gecko for me for at least another year. Or four. Which is
okay; I have no problem telling people to use Firefox for my (game)
application. But who knows, maybe Webkit will implement 1.7/1.8/etc.
before then. Opera and MSIE, forget it....

It is your decision to make. For Mozilla Foundation JavaScript
specific questions you may also ask at
mozilla.dev.tech.javascript (language specific)
and
mozilla.dev.tech.js-engine (engine specific)
They are rather regularly being read by people who are actually making
the things.

VK wrote:

[JScript]
There is a gap left between 5.6 and 7 for upcoming upgrades, and the
next version number in use is 7.0 for JScript.NET but this engine is
server-side only so out of your interest I guess.

JScript 5.7 for Windows XP (and probably 5.8 for Vista and Windows Server
2008) obviously exist, however I have yet to check if there are any
differences to JScript 5.6 or if the increase in version is only attributed
to them being introduced with different OS versions.

Other producers are using the original Netscape numbering schema with
JavaScript 1.0 for Netscape 2.x and JavaScript 1.5 being the current
industry standard de facto.

Other products simply do not support JScript or JavaScript. And if anything
is an industry standard right now, it is not JavaScript 1.5 but ECMAScript
(ECMA-262) Edition 3 or ISO/IEC 16262:2002.

JavaScript 1.5 is pretty much equal to JScript 5.6 lesser some minor
algorithm implementations.

Not true, as has been discussed here already.

JavaScript 1.6 (Firefox 1.5) and JavaScript 1.7 (Firefox 2.0) are
Mozilla Foundation proprietary extensions of the base 1.5

which also introduces proprietary features, however all of those
are backed up by the Specifications' Conformance sections.

Not all feature are backward compatible with 1.5, but any 1.5-
compliant program will run under 1.6 or 1.7

So overall you don't need to have any headache at all with versions
unless you want to use some of new Gecko-specific features.

Not true either, Often Wrong.

http://PointedEars.de/es-matrix


PointedEars
--
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
-- Richard Cornford, cljs, <f806at$ail$1$8300dec7 (AT) news (DOT) demon.co.uk>