<feed xmlns="http://www.w3.org/2005/Atom" xml:base="https://web-standards.dev" xml:lang="en">
	<title>Web Standards</title>
	<subtitle>Daily web platform news</subtitle>
	<link href="https://web-standards.dev"/>
	<link href="https://web-standards.dev/feed/" rel="self"/>
	<updated>2026-11-20T12:00:00+01:00</updated>
	<id>https://web-standards.dev/</id>
	<author>
		<name>Web Standards</name>
		<email>hi@web-standards.dev</email>
	</author>
		<entry>
			<title>Nudeps: bundler-like imports, none of the baggage</title>
			<link href="https://web-standards.dev/news/2026/11/nudeps-bundler-like-imports/"/>
			<updated>2026-11-20T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/nudeps-bundler-like-imports/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/nudeps-bundler-like-imports/cover.avif" width="1920" height="1080" alt="A cardboard box mascot holding a browser window, “nudeps: Bundler-like imports, none of the baggage”, and “Two steps, then forget it’s there” with install steps and code."&gt;
&lt;p&gt;Lea Verou introduces a tool that lets you import npm packages by name in the browser without a bundler. It copies only the needed files from &lt;code&gt;node_modules&lt;/code&gt; to &lt;code&gt;client_modules&lt;/code&gt; and generates an import map, never touching your own code. It works with Vue, React, Lit, D3, and even CJS packages. It doesn’t transform code, so JSX and TypeScript still need compilers, and only npm is supported for now.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://lea.verou.me/blog/2026/nudeps/&quot;&gt;lea.verou.me/blog/2026/nudeps&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Fingerprints are the new cookies</title>
			<link href="https://web-standards.dev/news/2026/11/fingerprints-are-the-new-cookies/"/>
			<updated>2026-11-19T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/fingerprints-are-the-new-cookies/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/fingerprints-are-the-new-cookies/cover.avif" width="1920" height="1080" alt="Title “Fingerprints are the new cookies”, a card “Giddy Beaver” with a SHA-256 hash, and “Try refreshing the page. Clear the cookies. Connect to a VPN. You’re still the Giddy Beaver.”"&gt;
&lt;p&gt;Marcin Szleszynski explains how browser fingerprinting is replacing third-party cookies, and how Google’s changes paved the way. He shows how a few lines of JavaScript combine &lt;code&gt;OfflineAudioContext&lt;/code&gt;, WebGL, canvas, &lt;code&gt;Intl&lt;/code&gt;, and &lt;code&gt;navigator&lt;/code&gt; signals, then hash them with SHA-256 into a nearly unique ID without any permission prompts.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://royfish.dev/fingerprints-are-the-new-cookies&quot;&gt;royfish.dev/fingerprints-are-the-new-cookies&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>What’s new in Chrome 158</title>
			<link href="https://web-standards.dev/news/2026/11/chrome-158/"/>
			<updated>2026-11-18T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/chrome-158/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/chrome-158/cover.avif" width="1920" height="1080" alt="Graphic with the text “New in Chrome” and the number 158, alongside the Chrome logo on a red grid background."&gt;
&lt;p&gt;The &lt;code&gt;&amp;lt;install&amp;gt;&lt;/code&gt; element and &lt;code&gt;navigator.install()&lt;/code&gt; let pages offer to install a web app, even cross-origin. Media pseudo-classes like &lt;code&gt;:playing&lt;/code&gt;, &lt;code&gt;:paused&lt;/code&gt;, and &lt;code&gt;:buffering&lt;/code&gt; style &lt;code&gt;&amp;lt;audio&amp;gt;&lt;/code&gt; and &lt;code&gt;&amp;lt;video&amp;gt;&lt;/code&gt; by playback state. The &lt;code&gt;::highlight(*)&lt;/code&gt; selector styles all custom highlights at once, &lt;code&gt;flow-start&lt;/code&gt; and &lt;code&gt;flow-end&lt;/code&gt; join the alignment keywords, and the &lt;code&gt;side&lt;/code&gt; attribute on &lt;code&gt;&amp;lt;textPath&amp;gt;&lt;/code&gt; moves text to the other side of a path. WebHID comes to Android.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://chromestatus.com/release-notes/158&quot;&gt;chromestatus.com/release-notes/158&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Introducing spatial CSS: a developer preview</title>
			<link href="https://web-standards.dev/news/2026/11/spatial-css-developer-preview/"/>
			<updated>2026-11-17T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/spatial-css-developer-preview/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/spatial-css-developer-preview/cover.avif" width="1920" height="1080" alt="Title “Introducing spatial CSS: A developer preview” in a WebKit puzzle playground window next to code and a 3D board with octagon, star, cross, and triangle pieces, by a snowy lake."&gt;
&lt;p&gt;Brandel Zachernuk presents a preview of the proposed spatial CSS API in Safari on visionOS 27.3, behind the CSS Portals flag. It extends existing syntax for 3D &lt;code&gt;&amp;lt;model&amp;gt;&lt;/code&gt; elements: &lt;code&gt;spatial: portal&lt;/code&gt; makes an element a shared 3D space, &lt;code&gt;transform&lt;/code&gt; moves models inside it, &lt;code&gt;position-anchor&lt;/code&gt; attaches one model to another, &lt;code&gt;@environment-map&lt;/code&gt; sets lighting from HDR images, and &lt;code&gt;portal-action: orbit&lt;/code&gt; lets users rotate the scene.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://webkit.org/blog/18621/introducing-spatial-css-a-developer-preview/&quot;&gt;webkit.org/blog/18621/introducing-spatial-css-a-developer-preview&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>The CSS caret-* properties and custom caret accessibility</title>
			<link href="https://web-standards.dev/news/2026/11/css-caret-properties-accessibility/"/>
			<updated>2026-11-16T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/css-caret-properties-accessibility/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/css-caret-properties-accessibility/cover.avif" width="1920" height="1080" alt="Title “The CSS caret-* properties and custom caret accessibility” above four text fields with auto, bar, block, and underscore carets, beside Sara Soueidan’s photo."&gt;
&lt;p&gt;Sara Soueidan explores &lt;code&gt;caret-color&lt;/code&gt;, &lt;code&gt;caret-shape&lt;/code&gt;, and &lt;code&gt;caret-animation&lt;/code&gt;, and how they affect the caret in text fields and in caret browsing. A custom caret needs 3:1 contrast, a fast blinking animation may fail WCAG flashing criteria, and custom styles can override caret preferences that users set in the OS. Be conservative and always add a visible focus indicator.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.sarasoueidan.com/blog/caret-styling-accessibility/&quot;&gt;sarasoueidan.com/blog/caret-styling-accessibility&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Framework performance</title>
			<link href="https://web-standards.dev/news/2026/11/framework-performance/"/>
			<updated>2026-11-13T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/framework-performance/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/framework-performance/cover.avif" width="1920" height="1080" alt="The e18e logo, title “Framework Performance”, sections Dev Time, Run Time, and Core Web Vitals, and a bar chart of framework timings from Astro at 89.00 ms to Next.js at 344.00 ms."&gt;
&lt;p&gt;A new project by e18e benchmarks nine meta-frameworks, from Astro and Next.js to Nuxt, SvelteKit, and TanStack Start: dependencies, install and build times, server throughput, and Core Web Vitals. Astro ships just 3KB on initial load and handles 767 requests per second. Next.js ships 140KB, handles 145, and is the only one that still ships &lt;code&gt;core-js&lt;/code&gt; polyfills. The tests run in CI for every new version.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://frameworks.e18e.dev/&quot;&gt;frameworks.e18e.dev&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Rebuilding the global town square from scratch</title>
			<link href="https://web-standards.dev/news/2026/11/rebuilding-global-town-square/"/>
			<updated>2026-11-12T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/rebuilding-global-town-square/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/rebuilding-global-town-square/cover.avif" width="1920" height="1080" alt="X logo and title “Rebuilding the global town square from scratch” above “Before” x.com/spacex with a splash screen at 13.7 s and “After” lite.x.com/spacex with the SpaceX profile at 2.7 s."&gt;
&lt;p&gt;Yagiz Nizipli explains how X replaced three servers for people, search crawlers, and link previews with one app on Vite, React, Fastify, and Relay. People get streaming HTML, verified crawlers get complete documents, and preview bots get only the head tags. On a slow connection, the first post now appears in 2.7 seconds instead of 23.9. Five engineers and AI agents built the app in under six months.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://blog.x.com/en/engineering/rebuilding-the-global-town-square-from-scratch&quot;&gt;blog.x.com/en/engineering/rebuilding-the-global-town-square-from-scratch&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Modern Web Guidance 1.0: the web platform expertise your coding agent is missing</title>
			<link href="https://web-standards.dev/news/2026/11/modern-web-guidance-1-0/"/>
			<updated>2026-11-11T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/modern-web-guidance-1-0/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/modern-web-guidance-1-0/cover.avif" width="1920" height="1080" alt="Title “Modern Web Guidance 1.0” next to a lantern-shaped logo made of curly braces with a star inside."&gt;
&lt;p&gt;Philip Walton announces the stable release of skills for coding agents, with Firefox and Edge joining Chrome to improve cross-browser compatibility. It adds a workflow that scans HTML, CSS, JS, and &lt;code&gt;package.json&lt;/code&gt; for safe upgrades, hundreds of verified AI knowledge gaps, and expert reviews.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://developer.chrome.com/blog/modern-web-guidance-v1&quot;&gt;developer.chrome.com/blog/modern-web-guidance-v1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Firefox 160 release notes for developers</title>
			<link href="https://web-standards.dev/news/2026/11/firefox-160/"/>
			<updated>2026-11-10T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/firefox-160/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/firefox-160/cover.avif" width="1920" height="1080" alt="Screenshot of browser developer tools with the Inspector panel open on web-standards.dev, a large Firefox logo overlaid, and the text “Firefox 160”."&gt;
&lt;p&gt;On-device speech recognition with the Web Speech API now works on desktop for real-time speech-to-text in 40 languages. WebTransport gets custom request headers, byte streams for datagrams, and new buffering options. The &lt;code&gt;::-webkit-input-placeholder&lt;/code&gt; pseudo-element now works as an alias of &lt;code&gt;::placeholder&lt;/code&gt;. Behind flags: &lt;code&gt;blocking=&amp;quot;render&amp;quot;&lt;/code&gt;, lazy loading for &lt;code&gt;&amp;lt;video&amp;gt;&lt;/code&gt; and &lt;code&gt;&amp;lt;audio&amp;gt;&lt;/code&gt;, and the &lt;code&gt;Speculation-Rules&lt;/code&gt; header.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/160&quot;&gt;developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/160&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>State of JavaScript 2026</title>
			<link href="https://web-standards.dev/news/2026/11/state-of-javascript-2026/"/>
			<updated>2026-11-09T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/state-of-javascript-2026/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/state-of-javascript-2026/cover.avif" width="1920" height="1080" alt="“State of JS 2026” logo with sections AI, Resources, About You, Features, Front-end Frameworks, Build Tools, Other Tools, Meta-Frameworks, Back-end Frameworks, and Testing."&gt;
&lt;p&gt;Sacha Greif and Devographics opened the survey for its tenth year, asking what role JavaScript still plays as AI agents, framework porting, and Rust rewrites reshape the ecosystem. It remains the gateway to the browser, so knowing the platform still matters. It takes about 15–20 minutes, and all questions are optional. Don’t forget to vote for your favorite resources and add anything new to your reading list.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://survey.devographics.com/en-US/survey/state-of-js/2026&quot;&gt;survey.devographics.com/en-US/survey/state-of-js/2026&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Beyond the viewport: introducing Site Seeing</title>
			<link href="https://web-standards.dev/news/2026/11/beyond-the-viewport-site-seeing/"/>
			<updated>2026-11-06T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/beyond-the-viewport-site-seeing/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/beyond-the-viewport-site-seeing/cover.avif" width="1920" height="1080" alt="Author’s photo, title “Responsive design is more than the viewport size”, and page previews labeled “Full browser”, “Developer Tools”, “Vertical tabs”, “Zoomed”, and “Phone”."&gt;
&lt;p&gt;Ahmad Shadeed built a tool that shows how a design behaves in contexts that force unusual viewport sizes, beyond just mobile and desktop. Modes include a full browser, open DevTools, vertical tabs, vertical tabs with DevTools, a zoomed-in page, a landscape phone, and print styles. Useful for designers, product managers, and developers to catch layouts that break where real users browse.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://ishadeed.com/article/beyond-the-viewport/&quot;&gt;ishadeed.com/article/beyond-the-viewport&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Safari introduces adaptive dark mode</title>
			<link href="https://web-standards.dev/news/2026/11/introducing-adaptive-dark-mode/"/>
			<updated>2026-11-05T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/introducing-adaptive-dark-mode/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/introducing-adaptive-dark-mode/cover.avif" width="1920" height="1080" alt="Title “Introducing Adaptive Dark Mode” beside the WebKit compass icon, above two Safari windows showing the same ArdenGo transit site in light and dark versions."&gt;
&lt;p&gt;The WebKit team presents a 27.3 beta feature that shows light websites as dark when the system is in dark mode. Sites with &lt;code&gt;color-scheme: light dark&lt;/code&gt; are left alone. Others get luminosity inverted with hue preserved, text contrast kept at 4.5:1, and simple logos and SVG icons adjusted. To opt out, use &lt;code&gt;color-scheme: light only&lt;/code&gt;. Better yet, build real dark mode with &lt;code&gt;prefers-color-scheme&lt;/code&gt; and &lt;code&gt;light-dark()&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://webkit.org/blog/18541/introducing-adaptive-dark-mode/&quot;&gt;webkit.org/blog/18541/introducing-adaptive-dark-mode&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>What’s new in Chrome 157</title>
			<link href="https://web-standards.dev/news/2026/11/chrome-157/"/>
			<updated>2026-11-04T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/chrome-157/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/chrome-157/cover.avif" width="1920" height="1080" alt="Graphic with the text “New in Chrome” and the number 157, alongside the Chrome logo on a blue grid background."&gt;
&lt;p&gt;HTML-in-canvas draws real HTML into &lt;code&gt;&amp;lt;canvas&amp;gt;&lt;/code&gt;. The new &lt;code&gt;corner&lt;/code&gt; shorthand sets &lt;code&gt;border-radius&lt;/code&gt; and &lt;code&gt;corner-shape&lt;/code&gt; at once, &lt;code&gt;text-overflow&lt;/code&gt; takes a custom string for clipped text, and &lt;code&gt;position-visibility&lt;/code&gt; gets the &lt;code&gt;anchor-valid&lt;/code&gt; and &lt;code&gt;anchor-visible&lt;/code&gt; values. Methods like &lt;code&gt;appendHTML()&lt;/code&gt; replace &lt;code&gt;insertAdjacentHTML()&lt;/code&gt;, &lt;code&gt;streamHTML()&lt;/code&gt; parses HTML as it arrives, and Long Animation Frames report style and layout time.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://chromestatus.com/release-notes/157&quot;&gt;chromestatus.com/release-notes/157&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Useful @custom-media presets</title>
			<link href="https://web-standards.dev/news/2026/11/useful-custom-media-presets/"/>
			<updated>2026-11-03T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/useful-custom-media-presets/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/useful-custom-media-presets/cover.avif" width="1920" height="1080" alt="Author’s photo, the title “Useful @custom-media Presets”, a red M logo, and two CSS snippets with @custom-media definitions and an @container style() fallback."&gt;
&lt;p&gt;Daniel Schwarz shares named media queries you can drop into any project. Input presets like &lt;code&gt;--mouse&lt;/code&gt;, &lt;code&gt;--touch&lt;/code&gt;, &lt;code&gt;--stylus&lt;/code&gt;, &lt;code&gt;--air&lt;/code&gt;, and &lt;code&gt;--dpad&lt;/code&gt; combine &lt;code&gt;hover&lt;/code&gt; and &lt;code&gt;pointer&lt;/code&gt; instead of guessing by screen size. Breakpoints go in 100px steps from &lt;code&gt;--from-360&lt;/code&gt; to &lt;code&gt;--from-1560&lt;/code&gt;, and &lt;code&gt;--true-hdr&lt;/code&gt; checks for HDR and P3. Only Firefox supports &lt;code&gt;@custom-media&lt;/code&gt;, behind a flag, so each preset also comes as &lt;code&gt;@container style()&lt;/code&gt;, or use PostCSS.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://blog.master.dev/useful-custom-media-presets/&quot;&gt;blog.master.dev/useful-custom-media-presets&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Cursors for base appearance</title>
			<link href="https://web-standards.dev/news/2026/11/cursors-for-base-appearance/"/>
			<updated>2026-11-02T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/11/cursors-for-base-appearance/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/11/cursors-for-base-appearance/cover.avif" width="1920" height="1080" alt="Comment by fantasai on GitHub issue “[css-forms-1] Cursors for base appearance #14251” with CSS rules for form control cursors and a red “Resolved” stamp."&gt;
&lt;p&gt;CSSWG settled the long-standing debate about whether interactive elements other than links should get &lt;code&gt;cursor: pointer&lt;/code&gt;. They should. In form controls with &lt;code&gt;appearance: base&lt;/code&gt;, buttons, &lt;code&gt;&amp;lt;select&amp;gt;&lt;/code&gt;, options, checkboxes, radios, and color pickers get &lt;code&gt;pointer&lt;/code&gt;, range sliders get &lt;code&gt;grab&lt;/code&gt;, disabled controls get &lt;code&gt;not-allowed&lt;/code&gt;, and read-only ones get &lt;code&gt;default&lt;/code&gt;. The logic: &lt;code&gt;pointer&lt;/code&gt; means “click this”.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/w3c/csswg-drafts/issues/14251&quot;&gt;github.com/w3c/csswg-drafts/issues/14251&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>The AI cost of JavaScript frameworks</title>
			<link href="https://web-standards.dev/news/2026/10/the-ai-cost-of-javascript-frameworks/"/>
			<updated>2026-10-30T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/10/the-ai-cost-of-javascript-frameworks/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/10/the-ai-cost-of-javascript-frameworks/cover.avif" width="1920" height="1080" alt="Title “The AI cost of JavaScript frameworks”, a bar chart “Cost per run, in US dollars” from Hono + htmx at $2.67 to Angular at $4.97, and the author’s photo."&gt;
&lt;p&gt;Nolan Lawson had agents build the same Pokémon app in 12 setups, from Angular and Next.js to Astro, Hono with htmx, and vanilla JavaScript. Hono with htmx was the cheapest at $2.67 per run with the least code. Angular was the most expensive at $4.97, the slowest, and the largest. Astro was the quickest to build and shipped almost no JavaScript. The benchmark is open, so you can pick a stack based on evidence, not vibes.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://nolanlawson.com/2026/10/28/the-ai-cost-of-javascript-frameworks/&quot;&gt;nolanlawson.com/2026/10/28/the-ai-cost-of-javascript-frameworks&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Embracing playful imperfection with the CSS random() function</title>
			<link href="https://web-standards.dev/news/2026/10/playful-imperfection-css-random/"/>
			<updated>2026-10-29T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/10/playful-imperfection-css-random/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/10/playful-imperfection-css-random/cover.avif" width="1920" height="1080" alt="Smashing Magazine logo, title “Embracing Playful Imperfection With The CSS random() Function”, “written by Brecht De Ruyte”, the author’s photo, and a red cat chasing a bird."&gt;
&lt;p&gt;Brecht De Ruyte shows how &lt;code&gt;random()&lt;/code&gt; takes a minimum, a maximum, and an optional step in matching units, so letters tilt, cards wobble, and marquee rows move at different speeds without JavaScript. Shared keys keep related properties in sync, and &lt;code&gt;element-scoped&lt;/code&gt; makes values unique per element. It’s already in Safari, Chrome, and Firefox behind a flag, so wrap it in &lt;code&gt;@supports&lt;/code&gt; and use it for decorative effects.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.smashingmagazine.com/2026/10/embracing-playful-imperfection-css-random-function/&quot;&gt;smashingmagazine.com/2026/10/embracing-playful-imperfection-css-random-function&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>WebKit features for Safari 27.1 and 27.2</title>
			<link href="https://web-standards.dev/news/2026/10/safari-27-1-and-27-2/"/>
			<updated>2026-10-28T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/10/safari-27-1-and-27-2/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/10/safari-27-1-and-27-2/cover.avif" width="1920" height="1080" alt="Safari Web Inspector Timelines for web-standards.dev with Layout &amp;amp; Rendering, JavaScript &amp;amp; Events, and CPU graphs, the Safari icon, and the headline “WebKit Features for Safari 27.1–27.2”."&gt;
&lt;p&gt;Jen Simmons covers two releases. Safari 27.1 brings Device Posture and Viewport Segments APIs for iPhone Duo behind flags, and two-page PDFs when folded. Safari 27.2 adds &lt;code&gt;::field-content&lt;/code&gt; for customizable &lt;code&gt;&amp;lt;select&amp;gt;&lt;/code&gt; and renames &lt;code&gt;flow-tolerance&lt;/code&gt; to &lt;code&gt;fit-tolerance&lt;/code&gt; in Grid Lanes. With &lt;code&gt;align-self: safe center&lt;/code&gt;, absolutely positioned boxes stay inside their container. Plus 20 bug fixes.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://webkit.org/blog/18486/webkit-features-for-safari-27-1/&quot;&gt;webkit.org/blog/18486/webkit-features-for-safari-27-1&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://webkit.org/blog/18515/webkit-features-for-safari-27-2/&quot;&gt;webkit.org/blog/18515/webkit-features-for-safari-27-2&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Firefox 159 release notes for developers</title>
			<link href="https://web-standards.dev/news/2026/10/firefox-159/"/>
			<updated>2026-10-27T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/10/firefox-159/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/10/firefox-159/cover.avif" width="1920" height="1080" alt="Screenshot of browser developer tools with the Inspector panel open on web-standards.dev, a large Firefox logo overlaid, and the text “Firefox 159”."&gt;
&lt;p&gt;Scroll-driven animations are now enabled by default, animating properties along a scroll-based timeline. Scoped custom element registries let each shadow tree have its own &lt;code&gt;CustomElementRegistry&lt;/code&gt;, avoiding name collisions between web components. The legacy masonry syntax is gone in favor of &lt;code&gt;display: grid-lanes&lt;/code&gt;. Plus, &lt;code&gt;setHTML()&lt;/code&gt; now sanitizes during parsing and WebGL gets new extensions.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/159&quot;&gt;developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/159&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Introducing the accessible components library</title>
			<link href="https://web-standards.dev/news/2026/10/accessible-components-library/"/>
			<updated>2026-10-26T12:00:00+01:00</updated>
			<id>https://web-standards.dev/news/2026/10/accessible-components-library/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/10/accessible-components-library/cover.avif" width="1920" height="1080" alt="Title “Introducing the Accessible Components Library”, “by Craig Abbott”, a toy brick with a code icon, author’s photo, and TetraLogical logo."&gt;
&lt;p&gt;Craig Abbott presents TetraLogical’s open-source library of eight components, including accordion, dialog, tabs, and text input, with HTML, CSS, and JS code and documentation. Each component maps to WCAG 2.2 criteria, written as Gherkin scenarios and run in a real browser via Cucumber and Playwright, using keyboard and mouse. About 97% of scenarios are automated, and the rest form a manual checklist.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://tetralogical.com/blog/2026/10/14/accessible-components-library/&quot;&gt;tetralogical.com/blog/2026/10/14/accessible-components-library&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>What the iPhone Duo means for web development (and Video.js)</title>
			<link href="https://web-standards.dev/news/2026/10/iphone-duo-web-development/"/>
			<updated>2026-10-23T12:00:00+02:00</updated>
			<id>https://web-standards.dev/news/2026/10/iphone-duo-web-development/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/10/iphone-duo-web-development/cover.avif" width="1920" height="1080" alt="VideoJS logo and title “What the iPhone Duo means for web development (and Video.js)” above orange, red, and purple stripes."&gt;
&lt;p&gt;Darius Cepulis found two Safari feature flags in the iPhone Duo simulator: the Device Posture API, which reports whether the screen is &lt;code&gt;continuous&lt;/code&gt; or &lt;code&gt;folded&lt;/code&gt;, and the Viewport Segments API, which exposes both halves via media queries and &lt;code&gt;env()&lt;/code&gt; variables. He used them to build a Netflix-style player with video on top and controls below. On a Pixel Fold emulator, fullscreen fills only the top half.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://videojs.org/blog/iphone-duo-web-development&quot;&gt;videojs.org/blog/iphone-duo-web-development&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Building a filterable menu that works for everyone</title>
			<link href="https://web-standards.dev/news/2026/10/filterable-menu-for-everyone/"/>
			<updated>2026-10-22T12:00:00+02:00</updated>
			<id>https://web-standards.dev/news/2026/10/filterable-menu-for-everyone/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/10/filterable-menu-for-everyone/cover.avif" width="1920" height="1080" alt="Title “Building a filterable menu that works for everyone”, an “Actions” menu with a “Move to folder” submenu filtered by “p”, a code sample, and the Base UI logo."&gt;
&lt;p&gt;Jenna Smith and James Nelson explain why Base UI’s filterable menu is a dialog with a search field rather than a combobox. Arrow keys highlight items via &lt;code&gt;aria-activedescendant&lt;/code&gt; while focus stays in the input, Home and End depend on whether there’s text, and each submenu gets its own input. The input uses &lt;code&gt;type=&amp;quot;text&amp;quot;&lt;/code&gt; with &lt;code&gt;role=&amp;quot;searchbox&amp;quot;&lt;/code&gt; to avoid native clear buttons, and focus isn’t trapped.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://base-ui.com/blog/building-a-filterable-menu&quot;&gt;base-ui.com/blog/building-a-filterable-menu&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>What’s new in Chrome 156</title>
			<link href="https://web-standards.dev/news/2026/10/chrome-156/"/>
			<updated>2026-10-21T12:00:00+02:00</updated>
			<id>https://web-standards.dev/news/2026/10/chrome-156/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/10/chrome-156/cover.avif" width="1920" height="1080" alt="Graphic with the text “New in Chrome” and the number 156, alongside the Chrome logo on a green grid background."&gt;
&lt;p&gt;CSS gets the &lt;code&gt;random()&lt;/code&gt; function for values in a range, the &lt;code&gt;:navigation-source&lt;/code&gt; pseudo-class for the link, button, or form that started a navigation, and the &lt;code&gt;pair&lt;/code&gt; keyword for &lt;code&gt;scroll-snap-type&lt;/code&gt; to snap both axes to the same element. Overflow accepts &lt;code&gt;scroll clip&lt;/code&gt; for single-axis scrolling. Failed module imports are no longer cached, so &lt;code&gt;import()&lt;/code&gt; can retry, WebTransport supports custom headers, and IndexedDB moves to a SQLite backend.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://chromestatus.com/release-notes/156&quot;&gt;chromestatus.com/release-notes/156&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>Why WebMCP matters</title>
			<link href="https://web-standards.dev/news/2026/10/why-webmcp-matters/"/>
			<updated>2026-10-20T12:00:00+02:00</updated>
			<id>https://web-standards.dev/news/2026/10/why-webmcp-matters/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/10/why-webmcp-matters/cover.avif" width="1920" height="1080" alt="Title “Why WebMCP matters”, subtitle “AKA WebMCP is Agentic WebPerf”, and author’s photo on a technical drawing of interlocking gears."&gt;
&lt;p&gt;Yoav Weiss, who shipped Shopify’s storefront WebMCP tools, argues that co-browsing is the only agentic model that keeps users in control, and WebMCP makes it fast. Sites register JS tools with schemas and descriptions, so agents call them instead of clicking around based on screenshots. Tests showed it 2.5-7.5x faster and up to 47x cheaper. He also answers WebKit’s concerns and explains why declarative WebMCP alone isn’t enough.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://blog.yoav.ws/posts/why_webmcp_matters/&quot;&gt;blog.yoav.ws/posts/why_webmcp_matters&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
		<entry>
			<title>JPEG XL vs AVIF for web use-cases</title>
			<link href="https://web-standards.dev/news/2026/10/jpeg-xl-vs-avif-for-web-use-cases/"/>
			<updated>2026-10-19T12:00:00+02:00</updated>
			<id>https://web-standards.dev/news/2026/10/jpeg-xl-vs-avif-for-web-use-cases/</id>
			<content type="html">
&lt;img src="https://web-standards.dev/news/2026/10/jpeg-xl-vs-avif-for-web-use-cases/cover.avif" width="1920" height="1080" alt="Title “JPEG XL vs AVIF” over a grid of six images: a red panda, a racing car, a cartoon cat, a neon “Senna” sign with cats, people holding phones, and a weasel."&gt;
&lt;p&gt;Jake Archibald benchmarked both formats on photos, screenshots, and images with transparency. AVIF wins at lossy compression: JPEG XL photos are typically 15–25% larger at default effort, and the gap is wider for screenshots and transparency. JPEG XL is the clear winner for lossless. His web default is AVIF 4:4:4 at the highest effort you can afford, with the jixel encoder for JPEG XL worth a try.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://jakearchibald.com/2026/jpeg-xl-vs-avif/&quot;&gt;jakearchibald.com/2026/jpeg-xl-vs-avif&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
	You can also follow us on
	&lt;a href="https://mastodon.social/@webstandards_dev"&gt;Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/web-standards.dev"&gt;Bluesky&lt;/a&gt;, &lt;a href="https://x.com/webstandardsdev"&gt;X&lt;/a&gt;
&lt;/p&gt;
			</content>
		</entry>
</feed>
