How Web/Browser APIs Work With V8 Engine
Diagram

- when Call Stack executes async code, it is passed to the browser to handle it
- once the browser is finished with it, a callback function is placed into the Callback Queue (if one exists)
- when Call Stack is empty, the Event Loop pops the first callback function in Callback Queue and places it into the Call Stack (the next callback function is popped when the Call Stack is empty)
- in reality, the Render Queue exists. It has higher priority than Callback Queue. So event Loop actually pops the Render Queue once every 0.016̅6 seconds, then from the Callback Queue
Todo
Closures - Scope - Scope Chain
- scope types & scope chain
- closures
- both
Checking Browser Support
JavaScript - Native
- JavaScript - Async Await (Enhancing Promises)
- JavaScript - function vs var function
- JavaScript - Promise
- JavaScript - Proxy
- JavaScript - Regular Functions / Function Declarations - Anonymous Functions / Function Expressions - Arrow Functions
JavaScript - Web/Browser APIs
- JavaScript - Browser Application
- JavaScript - Geolocation
- JavaScript - Navigator
- JavaScript - Web Animations API
- JavaScript - Web Audio API
- JavaScript - Web Components
- JavaScript - Web Real-Time Communication (WebRTC)
- JavaScript - Web Speech
- JavaScript - Web Worker
- JavaScript - WebGL 1 & 2
- JavaScript - WebGPU
- JavaScript - WebXR