Implement the JavaScript Standard

RESOLVED FIXED

Status

()

Core
JavaScript Engine
RESOLVED FIXED
5 years ago
2 years ago

People

(Reporter: emk, Unassigned)

Tracking

(Depends on: 1 bug, Blocks: 1 bug, {meta})

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [js:t], URL)

Comment hidden (empty)
(Reporter)

Updated

5 years ago
Depends on: 815014
(Reporter)

Updated

5 years ago
Keywords: meta
(Reporter)

Updated

5 years ago
Depends on: 815019

Comment 1

5 years ago
(In reply to Jeff Walden [:Waldo] (remove +bmo to email) from Bug 815014 comment #1)
> More generally, I have serious reservations about "standardizing", or even
> documenting, some of the things this "JavaScript spec" wants to standardize.
> Except in the specific sections where there is clear agreement, I think we
> should ignore it, and I don't think we should file bugs on so-called
> "deviations" from it.

(Just to have this documented in the "right" bug.)

Comment 2

5 years ago
I concur with comment #1. Many things in this document are controversial (defineGetter/defineSetter see bug 647423) or overlap with ECMAScript (Function#toString, __proto__).

Comment 3

5 years ago
(In reply to David Bruant from comment #2)
> […] overlap with ECMAScript (Function#toString, __proto__).

There shouldn’t be any overlap. http://javascript.spec.whatwg.org/ only aims to define what ECMAScript doesn’t.

The section on __proto__ already refers to the ES6 drafts and will be removed as soon as ES6 is finalized.

ES5 defines `Function#toString` as “an implementation-dependent representation of the function […] [that] has the syntax of a FunctionDeclaration”. I plan to compare existing implementations and define it properly in the JS spec.

Comment 4

5 years ago
(In reply to Mathias Bynens from comment #3)
> (In reply to David Bruant from comment #2)
> > […] overlap with ECMAScript (Function#toString, __proto__).
> 
> There shouldn’t be any overlap. http://javascript.spec.whatwg.org/ only aims
> to define what ECMAScript doesn’t.
Ok, thanks for the clarification.

> ES5 defines `Function#toString` as “an implementation-dependent
> representation of the function […] [that] has the syntax of a
> FunctionDeclaration”. I plan to compare existing implementations and define
> it properly in the JS spec.
ES6 is planning to spec Function#toString. See http://wiki.ecmascript.org/doku.php?id=harmony:function_to_string
If you do as you plan before ES6 is released, please send your feedback to es-discuss. We don't see enough of you there ;-)
Whiteboard: [js:t]
(Assignee)

Updated

4 years ago
Assignee: general → nobody

Comment 5

2 years ago
I think that Firefox fully implements the 22 July 2016 version...
(Reporter)

Comment 6

2 years ago
Sure.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.