Path to Stage 4!

[ljharb]

Stage 4

• committee approval
• implement in two browsers
  • node v12.0 (PR attempt 1 / PR attempt 2)
  • Chrome Canary / v8 (Bug)
    • Chrome v70 (flagged)
    • Chrome v71 (unflagged)
  • Firefox / SpiderMonkey (bug)
    • Firefox v65 Beta
    • Firefox v65 (unflagged)
  • Safari / Webkit / JSC (bug)
    • Safari 12.1 (unflagged)
    • Safari Technical Preview 73 (blog)
  • Edge / Chakra (issue / PR)
    • Edge (unflagged)
  • TypeScript (PR)
  • Hermes (commit)
• significant in-the-field experience
• resolve web compat issues (issue)
• ecma262 PR approved
• prepare ecma262 PR
• merge test262 tests
• write test262 tests (PR)

Stage 3

• committee approval
• spec editor signoff (Spec editor signoff #10)
• spec reviewer signoff (Spec reviewer signoff #9)
• receive implementor feedback
• flesh out naming research (Document detailed naming research #11, Still have not given conclusive examples of in-the-wild sites that will break by introducing properties named global or self or window #16)

Stage 2

• receive developer feedback
• committee approval
• spec text written
• spec reviewers selected

[chicoxyzzy]

Chrome started implementing global behind a flag https://bugs.chromium.org/p/v8/issues/detail?id=5537#c4

[ljharb]

Thanks; i'm subscribed and it's already linked in the OP :-)

[littledan]

Sorry that I am catching this a bit late, but I am wondering about the wording of this PR, which was set in this commit in response to this thread. I am wondering, how did you arrive at this wording, rather than using the wording in @domenic's suggestion?