Jump to content

JavaScript

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 210.193.53.1 (talk) at 03:50, 13 June 2008. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Insert non-form<nowiki><nowiki>Insert non-formatted text here</nowiki>atted text here</nowiki>

Not to be confused with Java (programming language).
For the use of JavaScript on Wikipedia, see Wikipedia:JavaScript.
JavaScript
ParadigmMulti-paradigm: prototype-based, functional, imperative, scripting
Designed byBrendan Eich
DeveloperNetscape Communications Corporation, Mozilla Foundation
First appeared1995
Stable release
1.7 / 2006
Typing disciplinedynamic, weak, duck
Websitewww.ecma-international.org/publications-and-standards/standards/ecma-262/
Major implementations
SpiderMonkey, Rhino, KJS, JavaScriptCore
Dialects
JScript, JScript .NET
Influenced by
Self, C, Scheme, Perl, Python, Java

JavaScript is a scripting language most often used for client-side web development. It was the originating dialect of the ECMAScript standard. It is a dynamic, weakly typed, prototype-based language with first-class functions. JavaScript was influenced by many languages and was designed to look like Java, but be easier for non-programmers to work with.[1][2]

Although best known for its use in websites (as client-side JavaScript), JavaScript is also used to enable scripting access to objects embedded in other applications (see below).

JavaScript, despite the name, is essentially unrelated to the Java programming language, although both have the common C syntax, and JavaScript copies many Java names and naming conventions. The language was originally named "LiveScript" but was renamed in a co-marketing deal between Netscape and Sun, in exchange for Netscape bundling Sun's Java runtime with their then-dominant browser. The key design principles within JavaScript are inherited from the Self programming language.

"JavaScript" is a trademark of Sun Microsystems. It was used under license for technology invented and implemented by Netscape Communications and current entities such as the Mozilla Foundation.[3]

History and naming

Some JavaScript source code

JavaScript was originally developed by Brendan Eich of Netscape under the name Mocha, which was later renamed to LiveScript, and finally to JavaScript. The language was originally implemented in Common Lisp (and retains many Lisp-like qualities).[4] The change of name from LiveScript to JavaScript roughly coincided with Netscape adding support for Java technology in its Netscape Navigator web browser. JavaScript was first introduced and deployed in the Netscape browser version 2.0B3 in December 1995. The naming has caused confusion, giving the impression that the language is a spin-off of Java, and it has been characterized by many as a marketing ploy by Netscape to give JavaScript the cachet of what was then the hot new web-programming language.[5][6]

Microsoft named its dialect of the language JScript to avoid trademark issues. JScript was first supported in Internet Explorer version 3.0, released in August 1996, and it included Y2K compliant date functions, unlike those based on java.util.Date in JavaScript at the time. The dialects are perceived to be so similar that the terms "JavaScript" and "JScript" are often used interchangeably (including in this article). Microsoft, however, notes dozens of ways in which JScript is not ECMA compliant.

Netscape submitted JavaScript to Ecma International for standardization resulting in the standardized version named ECMAScript.[7]

Features

Structured programming

JavaScript supports all the structured programming syntax in C (e.g., if statements, while loops, switch statements, etc.). One partial exception is scoping: C-style block-level scoping is not supported. However, JavaScript 1.7 supports block-level scoping with the let keyword.

Dynamic programming

dynamic typing
As in most scripting languages, types are associated with values, not variables. For example, a variable x could be bound to a number, then later rebound to a string. JavaScript supports various ways to test the type of an object, including duck typing.
objects as associative arrays
JavaScript is heavily object-based. Objects are associative arrays, such that object property names are associative array keys. obj.x = 10 and obj["x"] = 10 are equivalent, the dot notation being merely syntactic sugar. Properties and their values can be added, changed, or deleted at run-time. The properties of an object can also be enumerated via a for...in loop.
interpreted
Conforming JavaScript engines must be able to interpret (as opposed to compile) source code. This allows JavaScript to include an eval function.

Function-level programming

first-class functions
Functions are first-class; they are objects themselves. As such, they have properties and can be passed around and interacted with like any other object.
inner functions and closures
Inner functions (functions defined within other functions) are created each time the outer function is invoked, and variables of the outer functions for that invocation continue to exist as long as the inner functions still exist, even after that invocation is finished (e.g. if the inner function was returned, it still has access to the outer function's variables) — this is the mechanism behind closures within JavaScript.

Prototype-based

prototypes
JavaScript uses prototypes instead of classes for defining object properties, including methods, and inheritance. It is possible to simulate many class-based features with prototypes in JavaScript.
functions as object constructors
Functions double as object constructors along with their typical role. Prefixing a function call with new creates a new object and calls that function with its local this keyword bound to that object for that invocation. The function's prototype property determines the new object's prototype.
functions as methods
Unlike many object-oriented languages, there is no distinction between a function definition and a method definition. Rather, the distinction occurs during function calling; a function can be called as a method. When a function is invoked as a method of an object, the function's local this keyword is bound to that object for that invocation.

Others

run-time environment
JavaScript typically relies on a run-time environment (e.g. in a web browser) to provide objects and methods by which scripts can interact with "the outside world". (This is not a language feature per se, but it is common in most JavaScript implementations.)
variadic functions
An indefinite number of parameters can be passed to a function. The function can both access them through formal parameters and the local arguments object.
regular expressions
JavaScript also supports regular expressions in a manner similar to Perl, which provide a concise and powerful syntax for text manipulation that is more sophisticated than the built-in string functions.

Syntax

Further information: JavaScript syntax

As of 2008, the latest version of the language is JavaScript 1.8. The previous version 1.6 corresponded to ECMA-262 Edition 3 like JavaScript 1.5, except for Array extras, and Array and String generics. ECMAScript, in simple terms, is a standardized version of JavaScript. The ECMA-357 standard specifies E4X, a language extension dealing with XML.

Use in web pages

See also: Ajax (programming)

The primary use of JavaScript is to write functions that are embedded in or included from HTML pages and interact with the Document Object Model (DOM) of the page. Some simple examples of this usage are:

  • Opening or popping up a new window with programmatic control over the size, position and 'look' of the new window (i.e. whether the menus, toolbars, etc. are visible).
  • Validation of web form input values to make sure that they will be accepted before they are submitted to the server.
  • Changing images as the mouse cursor moves over them: This effect is often used to draw the user's attention to important links displayed as graphical elements.

Because JavaScript code can run locally in a user's browser (rather than on a remote server), it can respond to user actions quickly, making an application feel more responsive. Furthermore, JavaScript code can detect user actions which HTML alone cannot, such as individual keystrokes. Applications such as Gmail take advantage of this: much of the user-interface logic is written in JavaScript, and JavaScript dispatches requests for information (such as the content of an e-mail message) to the server. The wider trend of Ajax programming similarly exploits this strength.

A JavaScript engine (also known as JavaScript interpreter or JavaScript implementation) is an interpreter that interprets JavaScript source code and executes the script accordingly. The first ever JavaScript engine was created by Brendan Eich at Netscape Communications Corporation, for the Netscape Navigator web browser. The engine, code-named SpiderMonkey, is implemented in C. It has since been updated (in JavaScript 1.5) to conform to ECMA-262 Edition 3. The Rhino engine, created primarily by Norris Boyd (also at Netscape) is a JavaScript implementation in Java. Like SpiderMonkey, Rhino is ECMA-262 Edition 3 compliant.

By far, the most common host environment for JavaScript is a web browser. Web browsers typically use the public API to create "host objects" responsible for reflecting the DOM into JavaScript. The web server is another common application of the engine. A JavaScript webserver would expose host objects representing an HTTP request and response objects, which a JavaScript program could then manipulate to dynamically generate web pages.

A minimal example of a web page containing JavaScript (using HTML 4.01 syntax) would be: 

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head><title>simple page</title></head>
  <body>
    <script type="text/javascript">
      document.write('Hello World!');
    </script>
    <noscript>
      <p>Your browser either does not support JavaScript, or you have JavaScript turned off.</p>
    </noscript>
  </body>
</html>

Compatibility considerations

Main articles: Web Interoperability and Web accessibility

The DOM interfaces for manipulating web pages are not part of the ECMAScript standard, or of JavaScript itself. Officially, they are defined by a separate standardization effort by the W3C; in practice, browser implementations differ from the standards and from each other, and not all browsers execute JavaScript.

To deal with these differences, JavaScript authors can attempt to write standards-compliant code which will also be executed correctly by most browsers; failing that, they can write code that checks for the presence of certain browser features and behaves differently if they are not available.[8] In some cases, two browsers may both implement a feature but with different behavior, and authors may find it practical to detect what browser is running and change their script's behavior to match.[9][10] Programmers may also use libraries or toolkits which take browser differences into account.

Furthermore, scripts will not work for all users. For example, a user may:

  • use an old or rare browser with incomplete or unusual DOM support,
  • use a PDA or mobile phone browser which cannot execute JavaScript,
  • have JavaScript execution disabled as a security precaution,
  • or be visually or otherwise disabled and use a speech browser

To support these users, web authors can try to create pages which degrade gracefully on user agents (browsers) which do not support the page's JavaScript.

Security

JavaScript and the DOM provide the potential for malicious authors to deliver scripts to run on a client computer via the web. Browser authors contain this risk using two restrictions. First, scripts run in a sandbox in which they can only perform web-related actions, not general-purpose programming tasks like creating files. Second, scripts are constrained by the same origin policy: scripts from one web site do not have access to information such as usernames, passwords, or cookies sent to another site. Most JavaScript-related security bugs are breaches of either the same origin policy or the sandbox.

Cross-site vulnerabilities

Main articles: Cross-site scripting and Cross-site request forgery

A common JavaScript-related security problem is cross-site scripting, or XSS, a violation of the same origin policy. XSS vulnerabilities occur when an attacker is able to cause a trusted web site, such as an online banking website, to include a malicious script in the webpage presented to a victim. In that example, the script can then access the banking application with the privileges of the victim, potentially disclosing secret information or transferring money without the victim's authorization.

XSS vulnerabilities can also occur because of implementation mistakes by browser authors.[11]

XSS is related to, but not the same as, cross-site request forgery or XSRF. In XSRF, one website causes a victim's browser to generate fraudulent requests to another site, with the victim's legitimate HTTP cookies attached to the request.

Misunderstanding the client-server boundary

Client-server applications, whether they involve JavaScript or not, must assume that untrusted clients may be under the control of attackers. Thus any secret embedded in JavaScript could be extracted by a determined adversary, and the output of JavaScript operations should not be trusted by the server. Some implications:

  • Web site authors cannot perfectly conceal how their JavaScript operates, because the code is sent to the client, and obfuscated code can be reverse engineered.
  • JavaScript form validation only provides convenience for users, not security. If a site verifies that the user agreed to its terms of service, or filters invalid characters out of fields that should only contain numbers, it must do so on the server, not only the client.
  • It would be extremely bad practice to embed a password in JavaScript (where it can be extracted by an attacker), then have JavaScript verify a user's password and pass "password_ok=1" back to the server (since the "password_ok=1" response is easy to forge).[12]

Browser and plugin coding errors

JavaScript provides an interface to a wide range of browser capabilities, some of which may have flaws such as buffer overflows. These flaws can allow attackers to write scripts which would run any code they wish on the user's system.

These flaws have affected major browsers including Firefox[13], Internet Explorer[14], and Safari.[15]

Plugins, such as video players, Macromedia Flash, and the wide range of ActiveX controls enabled by default in Microsoft Internet Explorer, may also have flaws exploitable via JavaScript, and such flaws have been exploited in the past.[16][17] In Windows Vista, Microsoft has attempted to contain the risks of bugs such as buffer overflows by running the Internet Explorer process with limited privileges.[18]

Sandbox implementation errors

Web browsers are capable of running JavaScript outside of the sandbox, with the privileges necessary to, for example, create or delete files. Of course, such privileges aren't meant to be granted to code from the web.

Incorrectly granting privileges to JavaScript from the web has played a role in vulnerabilities in both Internet Explorer[19] and Firefox[20]. In Windows XP Service Pack 2, Microsoft tightened the rules on what JScript would be run with high privileges by Internet Explorer.[21]

Some versions of Microsoft Windows allow JavaScript stored on a computer's hard drive to run as a general-purpose, non-sandboxed program. This makes JavaScript (like VBScript) a theoretically viable vector for a Trojan horse, although JavaScript Trojan horses are uncommon in practice.[22] (See Windows Script Host.)

Uses outside web pages

Outside the web, JavaScript interpreters are embedded in a number of tools. Each of these applications provides its own object model which provides access to the host environment, with the core JavaScript language remaining mostly the same in each application.

  • ActionScript, the programming language used in Adobe Flash, is another implementation of the ECMAScript standard.
  • Apple's Dashboard Widgets, Microsoft's Gadgets, and Yahoo! Widgets are implemented using JavaScript.
  • The Mozilla platform, which underlies Firefox and some other web browsers, uses JavaScript to implement the graphical user interface (GUI) of its various products.
  • Adobe's Acrobat and Adobe Reader (formerly Acrobat Reader) support JavaScript in PDF files.
  • Tools in the Adobe Creative Suite, including Photoshop, Illustrator, Dreamweaver and InDesign, allow scripting through JavaScript.
  • Microsoft's Active Scripting technology supports the JavaScript-compatible JScript as an operating system scripting language.
  • The Java programming language, in version SE 6 (JDK 1.6), introduced the javax.script package, based on Mozilla Rhino. Thus, Java applications can host scripts that access the application's variables and objects, much like web browsers host scripts that access the browser's Document Object Model (DOM) for a webpage.[23][24]
  • Newer versions of the Qt C++ toolkit include a QtScript module to interpret JavaScript, analogous to javax.script.[25]
  • The interactive music signal processing software Max/MSP released by Cycling '74, offers a JavaScript model of its environment for use by developers. It allows much more precise control than the default GUI-centric programming model.
  • Late Night Software's JavaScript OSA (aka JavaScript for OSA, or JSOSA), is a freeware alternative to AppleScript for Mac OS X. It is based on the Mozilla 1.5 JavaScript implementation, with the addition of a MacOS object for interaction with the operating system and third-party applications.[26]
  • ECMAScript was included in the VRML97 standard for scripting nodes of VRML scene description files.
  • Some high-end Philips universal remote panels, including TSU9600 and TSU9400, can be scripted using JavaScript.[27]
  • Sphere[28] is an open source and cross platform computer program designed primarily to make role-playing games that uses JavaScript as scripting language.
  • Adobe Integrated Runtime is a JavaScript runtime that allows developers to create desktop applications.

Debugging

Within JavaScript, access to a debugger becomes invaluable when developing large, non-trivial programs. Because there can be implementation differences between the various browsers (particularly within the Document Object Model) it is useful to have access to a debugger for each of the browsers a web application is being targeted at.

Currently, Internet Explorer, Firefox, Safari, and Opera all have script debuggers available for them.

Internet Explorer has three debuggers available for it: Microsoft Visual Studio is the richest of the three, closely followed by Microsoft Script Editor (a component of Microsoft Office[29]), and finally the free Microsoft Script Debugger which is far more basic than the other two. The free Microsoft Visual Web Developer Express provides a limited version of the JavaScript debugging functionality in Microsoft Visual Studio.

Web applications within Firefox can be debugged using the Firebug plug-in, or the older Venkman debugger, which also works with the Mozilla browser. Drosera is a debugger for the WebKit engine[30] on Macintosh and Windows[31] powering Apple's Safari.

There are also some free tools such as JSLint, a code quality tool that will scan JavaScript code looking for problems[32], as well as a non-free tool called SplineTech JavaScript HTML Debugger.[33]

Since JavaScript is interpreted, loosely-typed, and may be hosted in varying environments, each with their own compatibility differences, a programmer has to take extra care to make sure the code executes as expected in as wide a range of circumstances as possible, and that functionality degrades gracefully when it does not.

Versions

Version Release date Equivalent to Netscape
Navigator		 Mozilla
Firefox		 Internet
Explorer		 Opera Safari
1.0 March 1996 2.0 3.0
1.1 August 1996 3.0
1.2 June 1997 4.0-4.05
1.3 October 1998 ECMA-262 1st edition / ECMA-262 2nd edition 4.06-4.7x 4.0
1.4 Netscape
Server
1.5 November 2000 ECMA-262 3rd edition 6.0 1.0 5.5 (JScript 5.5),
6 (JScript 5.6),
7 (JScript 5.7),
8 (JScript 6)
1.6 November 2005 1.5 + Array extras + Array and String generics + E4X 1.5
1.7 October 2006 1.6 + Pythonic generators + Iterators + let 2.0
1.8 1.7 + Generator expressions + Expression closures 3.0

The next major version of JavaScript, 2.0, will conform to ECMA-262 4th edition.[34]

There is not a particularly close genealogical relationship between Java and JavaScript; their similarities are mostly in basic syntax because both are ultimately derived from C. Their semantics are quite different and their object models are unrelated and largely incompatible. In Java, as in C and C++, all data is statically typed, whereas JavaScript variables, properties, and array elements may hold values of any type.

The standardization effort for JavaScript also needed to avoid trademark issues, so the ECMA 262 standard calls the language ECMAScript, three editions of which have been published since the work started in November 1996.

Microsoft's VBScript, like JavaScript, can be run client-side in web pages. VBScript has syntax derived from Visual Basic and is only supported by Microsoft's Internet Explorer.

JSON, or JavaScript Object Notation, is a general-purpose data interchange format that is defined as a subset of JavaScript.

JavaScript is also considered a functional programming language like Scheme and OCaml because it has closures and supports higher-order functions.[35]

See also

Wikibooks has a book on the topic of: Programming:JavaScript

References

  1. ^ TechVision: Innovators of the Net: Brendan Eich and JavaScript
  2. ^ Brendan's Roadmap Updates: Popularity
  3. ^ "Sun Trademarks". Sun Microsystems. Retrieved 2007-11-08.
  4. ^ Bill Clementson's Blog: JavaScript and Lisp
  5. ^ Programming languages used on the Internet and the World Wide Web (WWW)
  6. ^ O'Reilly - Safari Books Online - 0596101996 - JavaScript: The Definitive Guide, 5th Edition
  7. ^ Netscape Press Release
  8. ^ Peter-Paul Koch, Object detection
  9. ^ Peter-Paul Koch, Mission Impossible - mouse position
  10. ^ Peter-Paul Koch, Browser detect
  11. ^ MozillaZine, Mozilla Cross-Site Scripting Vulnerability Reported and Fixed
  12. ^ For an example of this bad practice, see http://javascript.internet.com/passwords/
  13. ^ Mozilla Corporation, Buffer overflow in crypto.signText()
  14. ^ Paul Festa, CNet, Buffer-overflow bug in IE
  15. ^ SecurityTracker.com, Apple Safari JavaScript Buffer Overflow Lets Remote Users Execute Arbitrary Code and HTTP Redirect Bug Lets Remote Users Access Files
  16. ^ SecurityFocus, Microsoft WebViewFolderIcon ActiveX Control Buffer Overflow Vulnerability
  17. ^ Fusion Authority, Macromedia Flash ActiveX Buffer Overflow
  18. ^ Mike Friedman, Protected Mode in Vista IE7
  19. ^ US CERT, Vulnerability Note VU#713878: Microsoft Internet Explorer does not properly validate source of redirected frame
  20. ^ Mozilla Foundation, Mozilla Foundation Security Advisory 2005-41: Privilege escalation via DOM property overrides
  21. ^ Microsoft Corporation, Changes to Functionality in Microsoft Windows XP Service Pack 2: Part 5: Enhanced Browsing Security
  22. ^ For one example of a rare JavaScript Trojan Horse, see Symantec Corporation, JS.Seeker.K
  23. ^ http://java.sun.com/javase/6/webnotes/index.html#scripting javax.script release notes
  24. ^ Flanagan 5th Edition, Pp 214 et seq
  25. ^ Trolltech ASA, QtScript Module
  26. ^ AppleScript#Open_Scripting_Architecture
  27. ^ Koninklijke Philips Electronics NV, [1]
  28. ^ Sphere[2]
  29. ^ JScript development in Microsoft Office 11 (MS InfoPath 2003)
  30. ^ Introducing Drosera - Surfin' Safari
  31. ^ Bug tracker discussion on Drosera Windows support
  32. ^ JSLint help page
  33. ^ SplineTech JavaScript HTML Debugger
  34. ^ Versions of JavaScript
  35. ^ The Little JavaScripter shows the relationship with Scheme in more detail.

Bibliography

  • McDuffie, Tina Spain (2003). JavaScript Concepts & Techniques: Programming Interactive Web Sites. Franklin, Beedle & Associates. ISBN 1-887-90269-4.
  • McFarlane, Nigel (2003). Rapid Application Development with Mozilla. Prentice Hall Professional Technical References. ISBN 0-13-142343-6.
  • Flanagan, David (2002). JavaScript: The Definitive Guide (4th Edition ed.). O'Reilly & Associates. ISBN 0-596-00048-0. {{cite book}}: |edition= has extra text (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  • Flanagan, David (2006). JavaScript: The Definitive Guide (5th Edition ed.). O'Reilly & Associates. ISBN 0-596-10199-6. {{cite book}}: |edition= has extra text (help)
  • Goodman, Danny (2003). JavaScript and DHTML Cookbook. O'Reilly & Associates. ISBN 0-596-00467-2. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  • Goodman, Danny (2001). JavaScript Bible. John Wiley & Sons. ISBN ISBN 0-7645-3342-8. {{cite book}}: Check |isbn= value: invalid character (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  • Watt, Andrew H. (2002). Teach Yourself JavaScript in 21 Days. Pearson Education. ISBN 0-672-32297-8. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  • Duffy, Scott (2003). How to do Everything with JavaScript. Osborne. ISBN 0-07-222887-3.
  • Harris, Andy (2001). JavaScript Programming for the Absolute Beginner. Premier Press. ISBN 0-7615-3410-5.
  • Burns, Joe (2001). JavaScript Goodies. Pearson Education. ISBN 0-7897-2612-2. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  • Shelly, Gary B. (2000). JavaScript: Complete Concepts and Techniques. Cambridge: Course Technology. ISBN 0-7895-6233-2. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  • Heinle, Nick (1997). Designing with JavaScript. O'Reilly & Associates. ISBN 1-56592-300-6. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  • Bhangal, Sham (2003). Foundation Web Design: Essential HTML, JavaScript, CSS, PhotoShop, Fireworks, and Flash. APress L. P. ISBN 1-59059-152-6. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  • Vander Veer, Emily A. (2004). JavaScript For Dummies (4th Edition ed.). Wiley Pub. ISBN 0-7645-7659-3. {{cite book}}: |edition= has extra text (help)
  • Powell, Thomas A. (2001). JavaScript: The Complete Reference. McGraw-Hill Companies. ISBN 0-07-219127-9. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
Retrieved from "https://en.wikipedia.org/w/index.php?title=JavaScript&oldid=219004873"