The Browser Platform for Frontend Developers
The browser platform is the set of built-in APIs JavaScript can use in a page: the DOM for reading and changing elements, events for user input, fetch for network requests, web storage for saving data, plus observers and workers for efficient and background work. Frameworks sit on top of these APIs.
Stage: JavaScript and TypeScript · Part of the Frontend Developer roadmap · Last reviewed 19 November 2026
What to learn in The Browser Platform
- Select elements and update the DOM safely with textContent
- Use event delegation so one listener handles many child elements
- Send a request with fetch and check response.ok before parsing JSON
- Choose between localStorage, sessionStorage and cookies for a given need
- Lazy-load content with IntersectionObserver instead of scroll handlers
The Browser Platform interview questions
What is event delegation and why use it?
Event delegation attaches one listener to a parent and uses event.target to find which child was clicked, relying on events bubbling up. It saves memory with long lists and works for elements added later, since you do not bind a handler to each new node.
Does fetch reject on a 404 response?
No. Fetch only rejects on network failures or aborts. A 404 or 500 still resolves with a Response whose ok property is false. You must check response.ok or the status yourself and throw if you want error handling to run in a catch block.
Where The Browser Platform fits in the Frontend Developer roadmap
The Browser Platform belongs to the JavaScript and TypeScript stage (beginner level), which takes about 5 hours. The language of the browser, and the type system that keeps large codebases sane.
Other units in this stage
Back to the full Frontend Developer roadmap