Home/Frontend
Topic

Frontend

1,551 articles on Frontend.

11,834 articles
Frontend — Loading WebAssembly modules efficiently

Loading WebAssembly modules efficiently

When working with WebAssembly, you often want to download a module, compile it, instantiate it, and then use whatever it exports in JavaScript. This post explains our recommended approach for optimal efficiency.

Wweb.dev·Frontend
Frontend — Media Source Extensions

Media Source Extensions

Media Source Extensions (MSE) is a JavaScript API that lets you build streams for playback from segments of audio or video.

Wweb.dev·Frontend
Frontend — CSS min(), max(), and clamp()

CSS min(), max(), and clamp()

Min, max, and clamp provide powerful CSS capabilities that enable more responsive styling with fewer liens of code. This post goes over how to control element sizing, maintain proper spacing, and implement fluid typography using these well-supported CSS math functions.

Wweb.dev·Frontend
Frontend — Preload modules

Preload modules

Module preload offers a way of declaratively loading JavaScript modules ahead of time.

Wweb.dev·Frontend
Frontend — prefers-reduced-motion: Sometimes less movement is more

prefers-reduced-motion: Sometimes less movement is more

The prefers-reduced-motion media query detects whether the user has requested that the system minimize the amount of animation or motion it uses. This is for users who either require or prefer minimized animations; for example people with vestibular disorders often prefer animations to be kept to a minimum.

Wweb.dev·Frontend
Frontend — Photoshop's journey to the web

Photoshop's journey to the web

Over the last three years, Chrome has been working to empower web applications that want to push the boundaries of what's possible in the browser. One such web application has been Photoshop. The idea of running software as complex as Photoshop directly in the browser would have been hard to imagine just a few years ago. However, by using various new web technologies, Adobe has now brought a publi

Wweb.dev·Frontend
Frontend — Same-origin policy

Same-origin policy

A browser can load and display resources from multiple sites. If there is no restriction on interactions between those resources, and if a script is compromised by an attacker, the script could expose everything on a user's browser.

Wweb.dev·Frontend
Frontend — Script evaluation and long tasks

Script evaluation and long tasks

When loading scripts, it takes time for the browser to evaluate them prior to execution, which can cause long tasks. Learn how script evaluation works, and what you can do to keep it from causing long tasks during page load.

Wweb.dev·Frontend
Frontend — Service workers and the Cache Storage API

Service workers and the Cache Storage API

The browser's HTTP cache is your first line of defense. It's not necessarily the most powerful or flexible approach, and you have limited control over the lifetime of cached responses. But there are several rules of thumb that give you a sensible caching implementation without much work, so you should always try to follow them.

Wweb.dev·Frontend
Frontend — Storage for the web

Storage for the web

There are many different options for storing data in the browser. Which one is best for your needs?

Wweb.dev·Frontend
Frontend — The UI fund

The UI fund

Announcing the UI fund from Chrome, designed to provide grants for people who work on design tools, CSS, and HTML.

Wweb.dev·Frontend
Frontend — Virtual reality comes to the web

Virtual reality comes to the web

Virtual reality came to the web in Chrome 79. Based on the WebXR Devicer API, this launch is the foundation for both augmented and virtual reality. This article is the first in a series, exploring basic concepts and describing how to enter an XR session. Other browsers will soon be supporting the WebXR Device API, including Firefox Reality, Oculus Browser, Edge and Magic Leap's Helio browser, amon

Wweb.dev·Frontend
Frontend — Virtual reality comes to the web, part II

Virtual reality comes to the web, part II

Virtual reality came to the web in Chrome 79. Based on the WebXR Device API, this launch is the foundation for both augmented and virtual reality. This article is the second in a series, focusing on the frame loop, the part of an XR session where images are shown to a viewer. Other browsers will soon be supporting the WebXR Device API, including Firefox Reality, Oculus Browser, Edge and Magic Leap

Wweb.dev·Frontend
Frontend — Web Components v1 - the next generation

Web Components v1 - the next generation

Web Components are gaining cross-browser support, the community is growing in leaps and bounds, and there’s a brand-new Web Component catalog to find exactly the component you need.

Wweb.dev·Frontend