Method added to `window` prefer using `this.` for console and other global properties

[ChildishGiant]

Issue Type: Bug

I'm not the only one with this issue, someone else pointed it out on Reddit 7 months ago but I haven't been able to find a report on here. Here's me reproducing it with no extensions on:

LawfulHealthyDugong

VS Code version: Code 1.42.1 (c47d83b293181d9be64f27ff093689e8e7aed054, 2020-02-11T14:45:59.656Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item	Value
CPUs	AMD Ryzen 5 1600X Six-Core Processor (12 x 3593)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off surface_control: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.93GB (6.49GB free)
Process Argv	E:\code\cloverleaf\web\cloverleaf.code-workspace
Screen Reader	no
VM	0%

[mjbvz]

Not ideal behavior but the reasons this is happening is because you are creating a method on the Window object so this inside the method is bound to window (which does have a console property). The code should still run in this case

[mjbvz]

Ideas:

• If this refers to the global type, don't include automatic this. member suggestions and instead prefer the normal global variable suggestions.

• See how common this problem actually is and possibly won't fix

[ChildishGiant]

Thanks so much for fixing my niche issue! ❤