tc39 proposal-global issues

tc39 / proposal-global

ECMAScript Proposal, specs, and reference implementation for `global`

http://tc39.github.io/proposal-global/

MIT License

349 stars 18 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Googleability

#49 mike-nelson closed 4 years ago
2
Better polyfill

#48 lygstate closed 4 years ago
1
MDN's documentation

#47 jwalton closed 5 years ago
19
Document use cases for wanting to access the global `this`

#46 mathiasbynens closed 4 years ago
1
Turn my pseudo-code into actual working demo code

#45 mathiasbynens closed 5 years ago
0
Clarify distinction between globalThis and the global object

#44 mathiasbynens closed 5 years ago
0
Polyfill does not work in an ES module context

#43 rictic closed 5 years ago
2
Why is this a data property rather than accessor property?

#42 annevk closed 5 years ago
9
Add a "use global" directive

#41 RohanTalip closed 5 years ago
5
Correct link to V8 intent to ship

#40 mathiasbynens closed 5 years ago
4
Naming suggestion: `globale`

#39 saschanaz closed 5 years ago
2
Naming suggestion: `esGlobal`

#38 manhinli closed 5 years ago
19
How about `standard` and `std` ?

#37 blfunex closed 5 years ago
4
Support `global` as alias of `globalThis` where possible

#36 ExE-Boss closed 5 years ago
2
Add more info about __global__

#35 styfle closed 5 years ago
1
Fix the formatting of the conclusion of NAMING.md

#34 j-f1 closed 5 years ago
0
Symbol.global

#33 nuragic closed 5 years ago
50
a set of names for consideration

#32 ianstormtaylor closed 5 years ago
208
Please use a name without `this` in it

#31 rauschma closed 5 years ago
59
Was "Global" name taken in consideration for naming?

#30 micnic closed 5 years ago
1
README: change one remaining global to globalThis

#29 mgol closed 5 years ago
0
Why not getting it from Object?

#28 mgtitimoli closed 5 years ago
5
Update the explainer

#27 littledan closed 5 years ago
2
Be careful to avoid conflating "global" with "realm"

#26 erights closed 5 years ago
1
update link to npm-package in README.md (current link is a deprecated package)

#25 kaizhu256 closed 5 years ago
0
update polyfill.js to use new-name

#24 kaizhu256 closed 5 years ago
2
Has import.meta.window been considered?

#23 guybedford closed 5 years ago
4
README: Clarify why `var globalWhatever = this` is insufficient

#22 mathiasbynens closed 5 years ago
0
Bug with JavaScript

#21 soroushm closed 6 years ago
1
global breaks flickr.com

#20 evilpie closed 5 years ago
111
global is writable

#19 evilpie closed 7 years ago
1
Cross realm global handling

#18 medikoo closed 7 years ago
3
Spec language for the global this value

#17 domenic closed 7 years ago
1
Still have not given conclusive examples of in-the-wild sites that will break by introducing properties named global or self or window

#16 domenic closed 7 years ago
18
Does global make sense

#15 annevk closed 8 years ago
17
`System.global` enumerability

#14 caridy closed 8 years ago
2
use PropertyDescriptor named schema to describe the property

#13 michaelficarra closed 8 years ago
2
Path to Stage 4!

#12 ljharb closed 4 years ago
21
Document detailed naming research

#11 ljharb closed 8 years ago
6
Spec editor signoff

#10 ljharb closed 7 years ago
8
Spec reviewer signoff

#9 ljharb closed 7 years ago
10
Removes typo }). Closes #7

#8 IAmAnubhavSaini closed 8 years ago
1
Typo?

#7 IAmAnubhavSaini closed 8 years ago
2
Is it problematic that System.global is a circular structure?

#6 joeldenning closed 8 years ago
3
System.environment

#5 petamoriken closed 8 years ago
1
Fix to not depend on closure environment

#4 dead-claudia closed 8 years ago
3
Use self?!

#3 annevk closed 8 years ago
6
polyfill VS native: possible enhancement

#2 WebReflection closed 8 years ago
1
Update README.md

#1 diklein closed 8 years ago
0