Bug 380236 (js1.8)

JS1.8 tracking bug

RESOLVED FIXED in mozilla1.9

Status

()

Core
JavaScript Engine
P3
normal
RESOLVED FIXED
10 years ago
8 years ago

People

(Reporter: brendan, Assigned: brendan)

Tracking

Trunk
mozilla1.9
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Assignee)

Description

10 years ago
JS1.8, to ship as part of Gecko 1.9, will be a smaller change from JS1.7 than 1.7 was from 1.6. But there are a few things we want to fix in 1.7 to track ES4/JS2, and a few more things from ES4 to implement and field-test:

- generator expressions
- JSON encoder and decoder
- slice syntax
- more and better array extras (see bug 363040)
- generalized destructuring for-in (bug 366941)

Missing dependency bugs coming soon.

/be
(Assignee)

Comment 1

10 years ago
Also:

- generator.close() automation only for a generator started by a for-in construct

This will simplify the GC, but require JSOP_ENDITER emulation by JSOP_SETSP so that close is automated when exiting a for-in due to an exception.

/be
(Assignee)

Comment 2

10 years ago
mrbkap, please propose bugs that we didn't fix for js1.7 (that one where let bindings turn into var bindings at top level, e.g.).

/be
Status: NEW → ASSIGNED

Comment 3

10 years ago
how about bug 238324?
(Assignee)

Updated

10 years ago
Depends on: 380237
(Assignee)

Comment 4

10 years ago
(In reply to comment #3)
> how about bug 238324?

That looks at a glance to be entirely outside of the core language and engine -- is it? Core language features such as packages should wait for JS2 on Tamarin (ActionMonkey), which will start development very soon but take longer than JS1.8. JS1.8 needs to be wrapped up pretty quickly.

/be
(In reply to comment #0)
> - JSON encoder and decoder

That's bug 340987.
(Assignee)

Updated

10 years ago
Depends on: 340987

Comment 6

10 years ago
(In reply to comment #1)
> Also:
> 
> - generator.close() automation only for a generator started by a for-in
> construct

Finally a sensible thing to do that would remove all that crazy stuff about close phase and its scheduling.

> 
> This will simplify the GC, but require JSOP_ENDITER emulation by JSOP_SETSP so
> that close is automated when exiting a for-in due to an exception.

This is bug 349326. I will try to implement it based on bug 379758 comment 1 during this week.
Depends on: 349326
Related (I think): can/should we make JS1.8 the default for XUL-loaded JS in Gecko 1.9?  We didn't in 1.8.1 for good compatibility reasons, but it makes for a lot of poking around by extension and app authors to get the right versioning parameters, and I think we'd do better by them in 1.9 to make the switch.
(Assignee)

Comment 8

10 years ago
(In reply to comment #7)
> Related (I think): can/should we make JS1.8 the default for XUL-loaded JS in
> Gecko 1.9?  We didn't in 1.8.1 for good compatibility reasons, but it makes for
> a lot of poking around by extension and app authors to get the right versioning
> parameters, and I think we'd do better by them in 1.9 to make the switch.

Please file that bug and make it block this one?

/be
(Assignee)

Comment 9

10 years ago
(In reply to comment #6)
> (In reply to comment #1)
> > Also:
> > 
> > - generator.close() automation only for a generator started by a for-in
> > construct
> 
> Finally a sensible thing to do that would remove all that crazy stuff about
> close phase and its scheduling.

Yes, JS1.7 followed Python too far there. Sorry about that.

> > This will simplify the GC, but require JSOP_ENDITER emulation by JSOP_SETSP so
> > that close is automated when exiting a for-in due to an exception.
> 
> This is bug 349326. I will try to implement it based on bug 379758 comment 1
> during this week.

Do you want to rip out the close phase in the same bug?

/be

Comment 10

10 years ago
(In reply to comment #9)
> > This is bug 349326. I will try to implement it based on bug 379758 comment 1
> > during this week.
> 
> Do you want to rip out the close phase in the same bug?

No. I prefer not to mix the patches implementing different things.
(Assignee)

Comment 11

10 years ago
(In reply to comment #10)
> No. I prefer not to mix the patches implementing different things.

Sounds good -- would you please file that bug and make it block this one? Thanks,

/be

Updated

10 years ago
Depends on: 380469

Comment 12

10 years ago
(In reply to comment #11)
> 
> would you please file that bug and make it block this one?

See bug 380469.

Updated

10 years ago
Depends on: 381031

Comment 13

10 years ago
(In reply to comment #7)
> Related (I think): can/should we make JS1.8 the default for XUL-loaded JS in
> Gecko 1.9? 
Filed bug 381031.
(Assignee)

Updated

10 years ago
Depends on: 381113
(Assignee)

Updated

10 years ago
Priority: -- → P1
Target Milestone: mozilla1.9alpha5 → mozilla1.9alpha6
(Assignee)

Updated

10 years ago
Depends on: 381372
Depends on: 381618

Updated

10 years ago
No longer depends on: 381618

Updated

10 years ago
Depends on: 382182
(Assignee)

Comment 14

10 years ago
We want to ban indirect eval, except for w.eval where w is a window object. Is there a bug on file already? I'm not sure we can pull this off before Mozilla 2, but it's worth considering.

/be
(Assignee)

Updated

10 years ago
Depends on: 363891
See bug 382509.
(Assignee)

Updated

10 years ago
Depends on: 383674
(Assignee)

Updated

10 years ago
Depends on: 384232
(Assignee)

Updated

10 years ago
Depends on: 384642
(Assignee)

Updated

10 years ago
Depends on: 382981
(Assignee)

Updated

10 years ago
Depends on: 384758
(Assignee)

Updated

10 years ago
Depends on: 376957
(Assignee)

Updated

10 years ago
Depends on: 98409
(Assignee)

Updated

10 years ago
Depends on: 402386
(Assignee)

Updated

10 years ago
Depends on: 404734
(Assignee)

Updated

10 years ago
Depends on: 408957
(Assignee)

Updated

10 years ago
Depends on: 409252
(Assignee)

Updated

10 years ago
Depends on: 346749
(Assignee)

Updated

10 years ago
Depends on: 229756
(Assignee)

Updated

10 years ago
Depends on: 410571
(Assignee)

Updated

10 years ago
Depends on: 408871
(Assignee)

Updated

10 years ago
Depends on: 416628
Depends on: 416636
(Assignee)

Updated

10 years ago
Depends on: 384991
(Assignee)

Comment 16

9 years ago
This bug should be closed soon. A doc-js1.8 bug may still be needed. Opinions?

/be
Target Milestone: mozilla1.9alpha6 → mozilla1.9

Updated

9 years ago
Depends on: 421027

Comment 17

9 years ago
I'll be tackling docs, I've already made some good headway:
http://developer.mozilla.org/en/docs/New_in_JavaScript_1.8

I'll go back through the recently-closed tickets and make sure everything lands in there. The tracking bug for doc-js1.8 is bug 421027.
(Assignee)

Comment 18

9 years ago
Waldo, you going to get to bug 416636 soon?

/be
No longer depends on: 229756

Updated

9 years ago
Blocks: 428420

Updated

9 years ago
No longer depends on: 384232

Updated

9 years ago
No longer depends on: 346749

Updated

9 years ago
No longer depends on: 340987
Depends on: 434013
(Assignee)

Updated

9 years ago
No longer depends on: 434013
Any updates on this? It would be nice to have a current SpiderMonkey release, with all the performance improvements that are in Fx3.
Dirkjan, for the source release, see bug 428420, which has quite a few blocking bugs, including some ugly crashes (that don't affect Firefox).

Updated

9 years ago
No longer blocks: 428420

Comment 21

9 years ago
I moved the dependencies from bug 428420 to here.
Blocks: 428420

Comment 22

9 years ago
reverting changes made in comment 21 due to bug 428420 comment 5.
No longer depends on: 349263, 378918, 412296, 419091, 420919, 429864, 430955, 434013, 438986
(Assignee)

Comment 23

8 years ago
1.8 is out. This bug should probably be closed and any depends-on bugs moved to a new tracker.

/be
Priority: P1 → P3
(Assignee)

Comment 24

8 years ago
I'm going to resolve this -- I think bug 421027 is resolved too, just not yet marked resolved.

/be
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
No longer depends on: 98409
Resolution: --- → FIXED

Updated

8 years ago
Depends on: 532652
You need to log in before you can comment on or make changes to this bug.