# Web Components

Web Components is a suite of web technologies for creating reusable custom elements with encapsulated functionality for web applications.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Vercel Releases UI SDK for Agents to Compose UI from Reusable Behaviors

DevFeed: [Vercel Releases UI SDK for Agents to Compose UI from Reusable Behaviors](<https://devfeed.tech/articles/vercel-releases-ui-sdk-for-agents-to-compose-ui-from-reusable-behaviors-140494.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/vercel-ui-sdk/>)

Author: Daniel Dominguez

Published: 2026-11-18T10:12:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [SDK](<https://devfeed.tech/topics/sdk.md>), [React](<https://devfeed.tech/topics/react.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Shadcn UI](<https://devfeed.tech/topics/shadcn-ui.md>)

Tags: [adapters](<https://devfeed.tech/tags/adapters.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [apache](<https://devfeed.tech/tags/apache.md>), [behaviors](<https://devfeed.tech/tags/behaviors.md>), [beta](<https://devfeed.tech/tags/beta.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [components](<https://devfeed.tech/tags/components.md>), [compose](<https://devfeed.tech/tags/compose.md>), [core](<https://devfeed.tech/tags/core.md>), [front-end](<https://devfeed.tech/tags/front-end.md>), [github](<https://devfeed.tech/tags/github.md>), [library](<https://devfeed.tech/tags/library.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [news](<https://devfeed.tech/tags/news.md>), [react](<https://devfeed.tech/tags/react.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [solid](<https://devfeed.tech/tags/solid.md>), [svelte](<https://devfeed.tech/tags/svelte.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [ui](<https://devfeed.tech/tags/ui.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [vercel-ui-sdk](<https://devfeed.tech/tags/vercel-ui-sdk.md>), [vue](<https://devfeed.tech/tags/vue.md>), [web-components](<https://devfeed.tech/tags/web-components.md>)

### AI overview

Vercel's beta UI SDK packages more than 50 interface behaviors--such as focus, selection, popups, and drag and drop--as reusable TypeScript helpers. Developers combine them into primitives, then render those primitives through React, Vue, Svelte, Solid, or Web Components; the same behaviors also support a starter set of unstyled components. Its agent bridge exposes component snapshots, queries, and actions without screenshots. Apps can approve or refuse agent steps, and change callbacks can identify and cancel agent-originated changes. Browser agents can use the same methods through WebMCP when the browser provides document.modelContext. The excerpt distinguishes UI SDK's focus on cross-framework behaviors and agent access from existing headless libraries, but offers no detailed feature-by-feature comparison. UI SDK is at 0.1.0-beta.1 under Apache 2.0 and public beta terms, so its APIs, documentation, and behavior may change. React requires version 19 or later; the other adapters document their own peer version ranges.

### Source excerpt

Vercel has released UI SDK in beta, an Apache 2.0 TypeScript library of more than 50 UI behaviors in @ui-sdk/core, with adapters for React, Vue, Svelte, Solid, and Web Components, so agents can compose accessible components and operate them through a documented agent bridge. By Daniel Dominguez

## Do web components have a future if nobody is writing them?

DevFeed: [Do web components have a future if nobody is writing them?](<https://devfeed.tech/articles/do-web-components-have-a-future-if-nobody-is-writing-them-90449.md>)

Original publisher: [Read original article](<https://nolanlawson.com/2026/10/19/do-web-components-have-a-future-if-nobody-is-writing-them/>)

Author: Nolan Lawson

Published: 2026-10-20T00:11:06Z

Content type: opinion

Language: en

Sources: [Read the Tea Leaves](<https://devfeed.tech/sources/read-the-tea-leaves.md>)

Topics: [Web Components](<https://devfeed.tech/topics/web-components.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [a2ui](<https://devfeed.tech/topics/a2ui.md>), [React](<https://devfeed.tech/topics/react.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic-coding](<https://devfeed.tech/tags/agentic-coding.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [web](<https://devfeed.tech/tags/web.md>), [web-components](<https://devfeed.tech/tags/web-components.md>)

### AI overview

The author argues that AI coding agents weaken web components' traditional value proposition of reusable components built on a common standard, as agents can generate interfaces from scratch. They suggest web components may remain useful for micro-frontends and framework-independent components, while pointing to unresolved server-side rendering, stylesheet sharing, and accessibility issues. The article also credits web components with shaping web platform standards.

### Source excerpt

With my previous post on "using the platform", I was surprised that the comments on Hacker News and Lobsters tended to veer toward web components. This surprised me because I didn't mention web components at all in the post. I was less surprised when I did some research and found that the entire...

## Shopify Upgrades Checkout Blocks to Polaris Web Components, Cutting Bundle Sizes up to 85%

DevFeed: [Shopify Upgrades Checkout Blocks to Polaris Web Components, Cutting Bundle Sizes up to 85%](<https://devfeed.tech/articles/shopify-upgrades-checkout-blocks-to-polaris-web-components-cutting-bundle-sizes-up-to-85-84361.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/shopify-web-components/>)

Author: Daniel Curtis

Published: 2026-10-09T15:01:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Shopify](<https://devfeed.tech/topics/shopify.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Preact.js](<https://devfeed.tech/topics/preact.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [versioning](<https://devfeed.tech/topics/versioning.md>)

Tags: [deployments](<https://devfeed.tech/tags/deployments.md>), [development](<https://devfeed.tech/tags/development.md>), [migration](<https://devfeed.tech/tags/migration.md>), [news](<https://devfeed.tech/tags/news.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [preact](<https://devfeed.tech/tags/preact.md>), [react](<https://devfeed.tech/tags/react.md>), [shopify](<https://devfeed.tech/tags/shopify.md>), [shopify-web-components](<https://devfeed.tech/tags/shopify-web-components.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [web-components](<https://devfeed.tech/tags/web-components.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

Shopify rewrote five high-traffic Checkout Blocks extensions using remote-dom, Preact, and Polaris web components, reducing bundle sizes by 40% to 85%. The changes also lowered median extension load time by about 8%. From October 1, 2026, deployments must use API version 2026-01 or later.

### Source excerpt

Shopify has updated its Checkout Blocks app, transitioning five high-traffic checkout UI extensions to remote-dom using Preact and Polaris web components. The rewrite, which involved moving to TypeScript and a new API version, led to significant reductions in bundle sizes and load times. From October 1, 2026, only the updated versions will be supported. By Daniel Curtis

## \<calc-input\>, a custom input element that accepts mathematical formulas

DevFeed: [\<calc-input\>, a custom input element that accepts mathematical formulas](<https://devfeed.tech/articles/calc-input-a-custom-input-element-that-accepts-mathematical-formulas-77509.md>)

Original publisher: [Read original article](<https://www.bram.us/2026/10/08/calc-input-a-custom-input-element-that-accepts-mathematical-formulas/>)

Author: Bramus!

Published: 2026-10-08T21:22:43Z

Content type: article

Language: en

Sources: [Bram.us](<https://devfeed.tech/sources/bram-us.md>)

Topics: [Web Components](<https://devfeed.tech/topics/web-components.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [LL parser](<https://devfeed.tech/topics/ll-parser.md>), [polynomials](<https://devfeed.tech/topics/polynomials.md>)

Tags: [calc](<https://devfeed.tech/tags/calc.md>), [calculator](<https://devfeed.tech/tags/calculator.md>), [component](<https://devfeed.tech/tags/component.md>), [css](<https://devfeed.tech/tags/css.md>), [custom-elements](<https://devfeed.tech/tags/custom-elements.md>), [form](<https://devfeed.tech/tags/form.md>), [forms](<https://devfeed.tech/tags/forms.md>), [html](<https://devfeed.tech/tags/html.md>), [input](<https://devfeed.tech/tags/input.md>), [math](<https://devfeed.tech/tags/math.md>), [original-content](<https://devfeed.tech/tags/original-content.md>)

### AI overview

The article introduces <calc-input>, a custom HTML input element for entering mathematical formulas in web forms. It displays the formula while focused and the calculated result when blurred, and uses a safe recursive-descent parser rather than eval(). It also describes form submission options, validation behavior, and styling.

### Source excerpt

Continuing my streak of small form-related Custom Elements (like <rich-input>), I built <calc-input>. It's a custom input element that accepts mathematical formulas -- such as 2 + 3 or (2 + 3) * 4 -- and automatically toggles between showing the formula on focus and the calculated result on blur.

## August 2026 Baseline monthly digest

DevFeed: [August 2026 Baseline monthly digest](<https://devfeed.tech/articles/august-2026-baseline-monthly-digest-85514.md>)

Original publisher: [Read original article](<https://web.dev/blog/baseline-digest-aug-2026?hl=en>)

Author: Jeremy Wagner GitHub LinkedIn Homepage

Published: 2026-09-28T07:00:00Z

Content type: article

Language: en

Sources: [web.dev](<https://devfeed.tech/sources/web-dev-blog.md>)

Topics: [Media Queries](<https://devfeed.tech/topics/media-queries.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Svelte](<https://devfeed.tech/topics/svelte.md>)

Tags: [begun](<https://devfeed.tech/tags/begun.md>), [calc](<https://devfeed.tech/tags/calc.md>), [class](<https://devfeed.tech/tags/class.md>), [css](<https://devfeed.tech/tags/css.md>), [feature](<https://devfeed.tech/tags/feature.md>), [features](<https://devfeed.tech/tags/features.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [helps](<https://devfeed.tech/tags/helps.md>), [html](<https://devfeed.tech/tags/html.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [monthly](<https://devfeed.tech/tags/monthly.md>)

### AI overview

The August 2026 Baseline digest reports on web platform features that became Newly available or Widely available, including CSS :paused and sibling-count(), plus Declarative Shadow DOM. It also highlights community guidance on using AI coding agents to write current, Baseline-aware CSS and HTML and maintain design system consistency.

### Source excerpt

Read about various happenings with Baseline during August 2026.

## datasette 1.0a41

DevFeed: [datasette 1.0a41](<https://devfeed.tech/articles/datasette-1-0a41-59604.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Sep/24/datasette/>)

Author: Simon Willison

Published: 2026-09-24T19:15:23Z

Content type: release

Language: en

Sources: [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>)

Tags: [alex-garcia](<https://devfeed.tech/tags/alex-garcia.md>), [alex-garcia-33](<https://devfeed.tech/tags/alex-garcia-33.md>), [datasette](<https://devfeed.tech/tags/datasette.md>), [datasette-1-547](<https://devfeed.tech/tags/datasette-1-547.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [javascript-765](<https://devfeed.tech/tags/javascript-765.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-4](<https://devfeed.tech/tags/opentelemetry-4.md>), [web-components](<https://devfeed.tech/tags/web-components.md>), [web-components-27](<https://devfeed.tech/tags/web-components-27.md>)

### AI overview

Datasette 1.0a41 adds OpenTelemetry support and refactors its modal dialogs into a single Web Component documented for use by other plugins.

### Source excerpt

Release: datasette 1.0a41 Alec Garcia added support for OpenTelemetry to Datasette in this release. I've also refactored all of Datasette's modal dialogs to a single Web Component, which is now documented for other plugins to use. Tags: javascript, datasette, web-components, alex-garcia, opentelemetry

## New in Edge for developers - Create better components and make your site agent-ready

DevFeed: [New in Edge for developers - Create better components and make your site agent-ready](<https://devfeed.tech/articles/new-in-edge-for-developers-create-better-components-and-make-your-site-agent-ready-57477.md>)

Original publisher: [Read original article](<https://blogs.windows.com/msedgedev/2026/09/21/new-in-edge-for-developers-create-better-components-and-make-your-site-agent-ready/>)

Author: Patrick Brosset

Published: 2026-09-21T16:58:01Z

Content type: release

Language: en

Sources: [Microsoft Edge](<https://devfeed.tech/sources/microsoft-edge-blog.md>)

Topics: [Edge](<https://devfeed.tech/topics/edge.md>), [Web](<https://devfeed.tech/topics/web.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [aria](<https://devfeed.tech/topics/aria.md>), [custom highlight api](<https://devfeed.tech/topics/custom-highlight-api.md>), [HTML](<https://devfeed.tech/topics/html.md>), [CSS](<https://devfeed.tech/topics/css.md>), [PWA](<https://devfeed.tech/topics/pwa.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [aria](<https://devfeed.tech/tags/aria.md>), [assistive-technology](<https://devfeed.tech/tags/assistive-technology.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [components](<https://devfeed.tech/tags/components.md>), [css](<https://devfeed.tech/tags/css.md>), [edge](<https://devfeed.tech/tags/edge.md>), [html](<https://devfeed.tech/tags/html.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [pwa](<https://devfeed.tech/tags/pwa.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>), [web](<https://devfeed.tech/tags/web.md>), [web-platform](<https://devfeed.tech/tags/web-platform.md>)

### AI overview

A Microsoft Edge developer roundup covers new web platform capabilities, including the OpaqueRange API for interacting with text ranges in form inputs, Shadow DOM reference support for accessible web components, and aria-actions for exposing secondary widget actions to assistive technologies. It also mentions media-state pseudo-classes, relative alpha colors, PWA drag regions, and early WebMCP features for browsing-agent scenarios.

### Source excerpt

Welcome back to New in Edge for developers, our recurring roundup of recent web platform updates in Microsoft Edge. In this edition, we'll look more closely at some of the newest additions to Microsoft Edge and the Chromium project, such as The post New in Edge for developers - Create better components and make your site agent-ready appeared first on Microsoft Edge Blog.

## Code Snacks

DevFeed: [Code Snacks](<https://devfeed.tech/articles/code-snacks-50967.md>)

Original publisher: [Read original article](<https://blog.master.dev/code-snacks/>)

Author: Chris Coyier

Published: 2026-09-15T15:19:26Z

Content type: article

Language: en

Sources: [Master.dev Blog RSS Feed](<https://devfeed.tech/sources/master-dev-blog-rss-feed.md>)

Topics: [Web Components](<https://devfeed.tech/topics/web-components.md>), [Code](<https://devfeed.tech/topics/code.md>), [Document Object Model (DOM)](<https://devfeed.tech/topics/dom.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [software-development](<https://devfeed.tech/topics/software-development.md>)

Tags: [animations](<https://devfeed.tech/tags/animations.md>), [code](<https://devfeed.tech/tags/code.md>), [components](<https://devfeed.tech/tags/components.md>), [dev](<https://devfeed.tech/tags/dev.md>), [git](<https://devfeed.tech/tags/git.md>), [the-beat](<https://devfeed.tech/tags/the-beat.md>), [web](<https://devfeed.tech/tags/web.md>), [web-components](<https://devfeed.tech/tags/web-components.md>), [web-platform](<https://devfeed.tech/tags/web-platform.md>)

### AI overview

The piece highlights short animations by Lauren Basser that explain technology concepts, including Working Directory and Shadow DOM, and recommends a Dave Rupert course for learning Web Components.

### Source excerpt

Love these little animations ("code snacks") from Lauren Basser that illustrate basic technological concepts. Check out the ones for Working Directory and Shadow DOM -- not the easiest concepts to illustrate as simply as this!

## Shadow-piercing local component variables

DevFeed: [Shadow-piercing local component variables](<https://devfeed.tech/articles/shadow-piercing-local-component-variables-49216.md>)

Original publisher: [Read original article](<https://daverupert.com/2026/08/how-to-pierce-your-shadow-belly-button/>)

Author: Dave Rupert

Published: 2026-08-17T15:14:00Z

Content type: article

Language: en

Sources: [Dave Rupert](<https://devfeed.tech/sources/daverupert-com.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Design system](<https://devfeed.tech/topics/design-system.md>)

Tags: [css](<https://devfeed.tech/tags/css.md>), [design-system](<https://devfeed.tech/tags/design-system.md>), [inheritance](<https://devfeed.tech/tags/inheritance.md>), [specificity](<https://devfeed.tech/tags/specificity.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [variables](<https://devfeed.tech/tags/variables.md>), [web-components](<https://devfeed.tech/tags/web-components.md>), [webcomponents](<https://devfeed.tech/tags/webcomponents.md>)

### AI overview

A front-end article explains how CSS custom properties behave in Web Components, including inheritance, specificity, and cascade interactions between global design-system tokens and local component variables. It discusses approaches for keeping themes flexible and avoiding overly specific element-coupled styling.

### Source excerpt

Edit (2026.08.24): Got feedback from the Web Components Community Group that I was mixing up inheritance, specificity, and the cascade and that * might be a better selector than :defined. I agree with both of those perspectives and I've updated this post. Stuart Robson's post Solving CSS @layer Ordering in Design Systems with Design Token Metadata, a response to Chris Coyier's Thinking Horizontally in CSS @layer, came to me at a serendipitous time. You know I love a good blog-and-response, but these posts on the topic of lowering the specificity of component-level tokens and scaling that out was a problem I was having with some of my web components. Their @layer trick didn't work for me, but here's what did... The local component variable problem Let's say we have a global stylesheet with our design system tokens. /* theme.css */ :root { --system-bg: #00f1; --system-fg: #000; --system-font: Inter, sans-serif; } And then we set up our web component with some local component variables that use design system tokens as defaults. <ui-card> <template shadowrootmode="open"> <style> :host { /* Local component variables */ --card-bg: var(--system-bg); --card-fg: var(--system-fg); --card-font: var(--system-font); /* Apply component styles */ background: var(--card-bg); color: var(--card-fg); font-family: var(--card-font); button { font-family: var(--card-font); } } </style> <slot></slot> </template> Hello world </ui-card> This works great... Except... I sort of expected that if we added some of those component tokens to the stylesheet we could restyle the card. /* theme.css - This doesn't work 😭 */ :root { /* ...system tokens go here... */ --card-bg: #f001; --card-fg: #f00; --card-font: fantasy; } :host has the same specificity as :root (0,1,0), but because :host declares the variables directly on the element, it replaces the inherited values. This confused even me, a web component front-end master, because there's a weird styling relationship in how :host overrides :root, but clas

## CodePen v2 adds a file explorer and support for multi-file and multi-page websites

DevFeed: [CodePen v2 adds a file explorer and support for multi-file and multi-page websites](<https://devfeed.tech/articles/the-new-yet-familiar-codepen-2-0-49214.md>)

Original publisher: [Read original article](<https://daverupert.com/2026/07/codepen-2/>)

Author: Dave Rupert

Published: 2026-07-27T04:50:00Z

Content type: release

Language: en

Sources: [Dave Rupert](<https://devfeed.tech/sources/daverupert-com.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [JSON](<https://devfeed.tech/topics/json.md>), [view transitions](<https://devfeed.tech/topics/view-transitions.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [components](<https://devfeed.tech/tags/components.md>), [file](<https://devfeed.tech/tags/file.md>), [file-system](<https://devfeed.tech/tags/file-system.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [json](<https://devfeed.tech/tags/json.md>), [release](<https://devfeed.tech/tags/release.md>), [ui](<https://devfeed.tech/tags/ui.md>), [view](<https://devfeed.tech/tags/view.md>), [web-components](<https://devfeed.tech/tags/web-components.md>)

### AI overview

CodePen v2 introduces a new editor with a file explorer, support for multi-file and multi-page websites, JavaScript module-style imports, and easier prototyping without a local development server.

### Source excerpt

CodePen v2 is now released! Because I co-host a podcast with Chris I've had an up-close perspective at this monumental effort over the last five years. I know how much work has gone into this release and I applaud the team for hitting the finish line. At the crux of the new experience is the new and improved editor. When you first launch into the v2.0 editor, your first response will probably be "Who moved my cheese!?" New is always uncomfortable, but there's a fix for getting back to the old familiar UI... Hit ⌘ + U or CTRL + U to hide the new pen sidebar Install the Classic Block Template to remove ~14 lines of HTML (Optional) Okay, now hit ⌘ + U or CTRL + U again, because what's in the sidebar are all the new features and favorite parts I want to talk about. An entire file system The first thing you'll notice when entering the new CodePen editor is a file explorer. That's right! CodePen is breaking out of its three-file constraint and allowing you to build entire multi-file and multi-page websites. A not-so-secret feature of CodePen was that you could mimic a file system in CodePen by using other pens as external resources, but referencing your custom reset.css by importing <user>/pen/<slug>.css wasn't the JS module-like experience you come to expect from the modern web. But gone are the days of 2,000 line JavaScript files, I can now import foo from './foo.js' like TC39 intended. I must admit that my more complex ideas were hitting the limit of what was comfortable to type into a tiny textbox. But now creating a folder of web components or JSON data files to loop through is easier than ever. I can build multi-file and multi-page prototypes (e.g. view-transitions! service-workers!) all without spinning up a local dev server. Digging up an old CodePen is much easier than finding an old folder on an old hard drive and it's arguably the easiest way to put a custom webpage up on the internet right now. Without drawing too many comparisons to competitors, CodePen at time

## A workaround for hiding empty slots in Chromium

DevFeed: [A workaround for hiding empty slots in Chromium](<https://devfeed.tech/articles/a-workaround-for-hiding-empty-slots-in-chromium-49212.md>)

Original publisher: [Read original article](<https://daverupert.com/2026/06/fix-for-host-has-slot/>)

Author: Dave Rupert

Published: 2026-06-19T04:57:00Z

Content type: tutorial

Language: en

Sources: [Dave Rupert](<https://devfeed.tech/sources/daverupert-com.md>)

Topics: [Web Components](<https://devfeed.tech/topics/web-components.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Document Object Model (DOM)](<https://devfeed.tech/topics/dom.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [bug](<https://devfeed.tech/tags/bug.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [css](<https://devfeed.tech/tags/css.md>), [flex](<https://devfeed.tech/tags/flex.md>), [grid](<https://devfeed.tech/tags/grid.md>), [layout](<https://devfeed.tech/tags/layout.md>), [web-components](<https://devfeed.tech/tags/web-components.md>), [webcomponents](<https://devfeed.tech/tags/webcomponents.md>)

### AI overview

A workaround for hiding empty named slots in Web Components when Chromium fails to support the relevant :host(:has([slot])) query. The article explains how this causes ghost gaps in flex or grid layouts and reports a solution that works in Safari, Firefox, and Chrome.

### Source excerpt

Named slots are one of web components' biggest superpowers ✨. Imagine a Button component with an optional icon; in Web Components we don't need a separate Button and IconButton, a single Button component with <slot name="icon"> will do. Or a card component with a handful of predefined slots for image, title, description, price, metadata, etc. Not 100 different cards... one card. Slots are a wonderful way to declaratively compose UI, but one shadow styling challenge that has vexed my team over the years is how to contextually hide a <slot> when there's no slotted content. The problem... ghost gaps The most idiomatic way to check if a particular slot is in-use is to use :host(:has([slot="foo"])). But... In a weird twist to how web component browser-compat bugs tend to go, :host(:has([slot])) works in Safari and Firefox today but doesn't work in Chromium! Chromium not supporting :host(:has([slot])) means we can't query an element's Light DOM contents from the Shadow DOM. That interpretation of encapsulation makes sense (I guess) and in most situations it's not a big problem; an empty slot is like an empty span and probably won't impact rendering. But it becomes a problem when the empty slots appear in a flex or grid layout using gap because unless you hide the element and/or its wrapper, the gap will not collapse in Chromium, so you end up with a "ghost gap". Example: With slot="optional" content in Light DOM Required content Optional content - expected: show content with gap <optional-slot-demo-broken> <div slot="required">Required content</div> <div slot="optional">Optional content - expected: show content with gap</div> </optional-slot-demo-broken> Example: Without slot="optional" content in Light DOM Required content <optional-slot-demo-broken> <div slot="required">Required content</div> <!-- expected: does not show extra whitespace --> </optional-slot-demo-broken> ✅ Works in Safari = wrapper div hidden, no gap ✅ Works in Firefox = wrapper div hidden, no gap ❌ Broken in

## Four Mechanisms Behind EGP Code, an AI-Powered Landing Page Editor

DevFeed: [Four Mechanisms Behind EGP Code, an AI-Powered Landing Page Editor](<https://devfeed.tech/articles/four-mechanisms-behind-egp-code-an-ai-powered-landing-page-editor-56815.md>)

Original publisher: [Read original article](<https://engineering.mercari.com/en/blog/entry/20260610-how-egp-code-works/>)

Author: Mattsuu

Published: 2026-06-10T11:00:58Z

Content type: article

Language: en

Sources: [Mercari Engineering](<https://devfeed.tech/sources/mercari-engineering.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Firestore](<https://devfeed.tech/topics/firestore.md>), [data](<https://devfeed.tech/topics/data.md>), [test](<https://devfeed.tech/topics/test.md>), [API](<https://devfeed.tech/topics/api.md>), [lint](<https://devfeed.tech/topics/lint.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [css](<https://devfeed.tech/tags/css.md>), [errors](<https://devfeed.tech/tags/errors.md>), [firestore](<https://devfeed.tech/tags/firestore.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [lint](<https://devfeed.tech/tags/lint.md>)

### AI overview

This article explains four mechanisms inside EGP Code, Merpay's internal AI editor for building landing pages: a recursive agent loop, real-time synchronization through Firestore, browser-based testing, and a mapping table connecting preview elements to HTML. It also describes how the editor combines AI instructions, manual HTML editing, previewing, and publishing.

### Source excerpt

Hi, I'm @mattsuu a frontend engineer at Merpay. This is Day 7 of Merpay & Mercoin Tech Openness Month 2026. EGP Code is an internal editor for building landing pages (LPs) with AI. We covered the background in Why we built EGP Code, an HTML-based AI editor for landing pages; this article digs into four [...]

## Bringing the real world to your AI application using Firebase AI Logic

DevFeed: [Bringing the real world to your AI application using Firebase AI Logic](<https://devfeed.tech/articles/bringing-the-real-world-to-your-ai-application-using-firebase-ai-logic-16663.md>)

Original publisher: [Read original article](<https://firebase.blog/posts/2026/05/ai-logic-maps-grounding>)

Author: Ankita Saxena; Ken Nevarez

Published: 2026-05-19T00:00:00Z

Content type: tutorial

Language: en

Sources: [Firebase Blog](<https://devfeed.tech/sources/firebase-blog.md>)

Topics: [Firebase](<https://devfeed.tech/topics/firebase.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Google Maps](<https://devfeed.tech/topics/google-maps.md>), [Generative AI](<https://devfeed.tech/topics/generative-ai.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [API](<https://devfeed.tech/topics/api.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-logic](<https://devfeed.tech/tags/ai-logic.md>), [api](<https://devfeed.tech/tags/api.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [firebase-ai-logic](<https://devfeed.tech/tags/firebase-ai-logic.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [google-maps](<https://devfeed.tech/tags/google-maps.md>), [hallucinations](<https://devfeed.tech/tags/hallucinations.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Firebase introduces Grounding with Google Maps in the Firebase AI Logic SDK to help mobile and web applications produce location-aware responses based on real-world geospatial data. The article explains configuring the model, plotting places with Google Maps Web Components, and using grounding metadata for citations and coordinates.

### Source excerpt

News, tutorials, and updates from the Firebase team.

## Declarative Shadow DOM and Native Server-Side Rendering

DevFeed: [Declarative Shadow DOM and Native Server-Side Rendering](<https://devfeed.tech/articles/declarative-shadow-dom-and-native-server-side-rendering-49243.md>)

Original publisher: [Read original article](<https://www.debugbear.com/blog/declarative-shadow-dom>)

Author: Anna Monus

Published: 2026-04-29T00:00:00Z

Content type: tutorial

Language: en

Sources: [DebugBear Blog](<https://devfeed.tech/sources/debugbear-blog.md>)

Topics: [Web Components](<https://devfeed.tech/topics/web-components.md>), [Server-side rendering](<https://devfeed.tech/topics/server-side-rendering.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [Document Object Model (DOM)](<https://devfeed.tech/topics/dom.md>), [HTML](<https://devfeed.tech/topics/html.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>)

Tags: [components](<https://devfeed.tech/tags/components.md>), [core-web-vitals](<https://devfeed.tech/tags/core-web-vitals.md>), [css](<https://devfeed.tech/tags/css.md>), [custom-elements](<https://devfeed.tech/tags/custom-elements.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [html-elements](<https://devfeed.tech/tags/html-elements.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [polyfill](<https://devfeed.tech/tags/polyfill.md>), [server-side-rendering](<https://devfeed.tech/tags/server-side-rendering.md>), [web-components](<https://devfeed.tech/tags/web-components.md>)

### AI overview

Declarative Shadow DOM enables server-side rendering of encapsulated Web Components by allowing shadow roots to be declared directly in HTML. This lets browsers render content without JavaScript and can improve when content becomes visible and Core Web Vitals.

### Source excerpt

Declarative Shadow DOM (DSD) makes server-side rendering of Web Components possible, which can meaningfully improve page load times and Core Web Vitals.

## Web Weekly #187 (#blogPost)

DevFeed: [Web Weekly #187 (#blogPost)](<https://devfeed.tech/articles/web-weekly-187-blogpost-45422.md>)

Original publisher: [Read original article](<https://www.stefanjudis.com/blog/web-weekly-187/>)

Published: 2026-03-16T23:00:00Z

Content type: article

Language: en

Sources: [Stefan Judis Web Development](<https://devfeed.tech/sources/stefan-judis-web-development.md>)

Topics: [Web Development](<https://devfeed.tech/topics/web-development.md>), [CSS](<https://devfeed.tech/topics/css.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [polyfill](<https://devfeed.tech/topics/polyfill.md>), [view transitions](<https://devfeed.tech/topics/view-transitions.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [aria](<https://devfeed.tech/topics/aria.md>)

Tags: [accessible](<https://devfeed.tech/tags/accessible.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-slop](<https://devfeed.tech/tags/ai-slop.md>), [aliases](<https://devfeed.tech/tags/aliases.md>), [anchor-positioning](<https://devfeed.tech/tags/anchor-positioning.md>), [blogpost](<https://devfeed.tech/tags/blogpost.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [code](<https://devfeed.tech/tags/code.md>), [color](<https://devfeed.tech/tags/color.md>), [colors](<https://devfeed.tech/tags/colors.md>), [css](<https://devfeed.tech/tags/css.md>), [custom-elements](<https://devfeed.tech/tags/custom-elements.md>), [elements](<https://devfeed.tech/tags/elements.md>), [function](<https://devfeed.tech/tags/function.md>), [github](<https://devfeed.tech/tags/github.md>), [github-sponsors](<https://devfeed.tech/tags/github-sponsors.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [newsletter](<https://devfeed.tech/tags/newsletter.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [web](<https://devfeed.tech/tags/web.md>), [weekly](<https://devfeed.tech/tags/weekly.md>)

### AI overview

Web Weekly #187 highlights emerging web platform features and their limitations. The newsletter says `contrast-color()` is planned across browsers with Chrome 147 but currently returns only black or white; Una describes a workaround. Chromium's experimental `focusgroup` attribute aims to simplify custom focus handling and set ARIA roles automatically, though the author notes skepticism and invites feedback. Other items cover form-associated custom elements and `attachInternals()`, a non-visual view-transition polyfill, JSON import attributes and caching, customizable `select` elements, and custom import paths in Node.js. The CSS `at-rule()` feature is not yet broadly supported and is expected in Chrome 148; CSS unit conversion with `.to()` is also not available in all browsers. The newsletter additionally notes Firefox 148 baseline support for CSS `shape()` with `offset-path` or `clip-path`.

### Source excerpt

Guten Tag! Guten Tag! 👋 Have you heard of focusgroup? Did you try aliases in Node.js imports already? Or do you know that CSS is available in JavaScript? Turn on the Web Weekly tune and find some answers below. Enjoy! Mario listens to "Ethel Cain - Waco, Texas" and says: This is my kind of opera. Do you want to share your favorite song with the Web Weekly community? Hit reply; there are four more songs left in the queue. If you enjoy Web Weekly, share it with your friends and family. 🦋 Bluesky 🐘 Mastodon 💼 Linkedin A quick "repost" really helps this indie newsletter out. Thank you! ❤ Web Weekly housekeeping A big thank you and a huge bag of karma points go to Jonathan this week. Thank you for supporting indie publishing in the times of AI slop by covering a small fraction of the cost it takes to send Web Weekly every week! My little side project is now supported by 40 people. This makes me incredibly happy (and proud). ❤ You can support Web Weekly on Patreon or GitHub Sponsors. And also, I messed up a link last week. I clicked all the links before sending the email, but because last week was an "unofficial Temami edition", I didn't recognize that I linked to the wrong post. Here's the correct link to anchor positioning issues. Sorry! No code I didn't discover good "No code" articles this week. Did you read something great beyond coding lately? I'd love to read it, too! color-contrast() beyond black & white With Chrome 147 (planned for Mar 25), the contrast-color() function will be newly available across all browsers. Theoretically, the function lets you throw a color in and get an accessible contrast color out. It's a great idea, but contrast-color() is limited to returning black or white right now. Una describes how to work around this limitation. Mix all the colors Form-associated custom elements Granted, Rob's article is very long, but the intro paragraphs make it worth reading already. I've seen the attachInternals() method quite a few times in custom elements

## 15 years of blogging

DevFeed: [15 years of blogging](<https://devfeed.tech/articles/15-years-of-blogging-45702.md>)

Original publisher: [Read original article](<https://nolanlawson.com/2026/02/01/15-years-of-blogging/>)

Author: Nolan Lawson

Published: 2026-02-01T16:11:07Z

Content type: opinion

Language: en

Sources: [Read the Tea Leaves](<https://devfeed.tech/sources/read-the-tea-leaves.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Android](<https://devfeed.tech/topics/android.md>), [CSS](<https://devfeed.tech/topics/css.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [android](<https://devfeed.tech/tags/android.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [blogging](<https://devfeed.tech/tags/blogging.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [life](<https://devfeed.tech/tags/life.md>), [web-components](<https://devfeed.tech/tags/web-components.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

A retrospective on 15 years of blogging, covering the author's career trajectory from machine learning and Android to JavaScript, web development, web performance, accessibility, and web components. It also reflects on the challenges and anxieties of writing for a public audience.

### Source excerpt

My first blog post was published just under 15 years ago in March of 2011. Since then, I've published 151 posts, including this one. (If I was a numerologist, I'd think it had something to do with Pokémon.) This blog has covered a wide variety of topics, including Pokémon in fact (I wrote the first [...]

## Dealbreaker bugs in native popovers

DevFeed: [Dealbreaker bugs in native popovers](<https://devfeed.tech/articles/dealbreaker-bugs-in-native-popovers-52337.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2025/deal-breaker-bugs-in-popovers>)

Author: Manuel Matuzović

Published: 2025-12-05T00:00:00Z

Content type: article

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [bug](<https://devfeed.tech/topics/bug.md>), [HTML](<https://devfeed.tech/topics/html.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browser-bugs](<https://devfeed.tech/tags/browser-bugs.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [html](<https://devfeed.tech/tags/html.md>), [keyboard](<https://devfeed.tech/tags/keyboard.md>), [web-components](<https://devfeed.tech/tags/web-components.md>)

### AI overview

An accessibility bug in native HTML popovers causes keyboard focus to skip focusable elements when popovers contain slots or a details element. The issue affects Chromium-based browsers and Firefox versions below 145, creating problems for reusable web-component pattern libraries.

### Source excerpt

One of my clients decided to write a custom popover component that uses native popovers under the hood. We built the component and were happy with it. They were about to ship it until we realised there was an accessibility bug so severe that it was a dealbreaker for us. Popovers are floating UI elements you can show or hide by pressing a button. They come with many accessibility features built in, so you don't have to handle most of the work. You can learn more about that in "The accessibility of the popover attribute" (YouTube). All you need to use popovers is the popover and popovertarget attributes. <button popovertarget="popover-html">HTML</button> <div popover id="popover-html"> Hypertext Markup Language (HTML) is the standard markup language for documents designed to be displayed in a web browser. </div> Try it yourself: HTML Hypertext Markup Language (HTML) is the standard markup language for documents designed to be displayed in a web browser. Bugs Popovers can contain focusable elements, such as buttons. In the following example, if you use the keyboard and focus the first button, press Enter, and press Tab again, you can see how focus jumps from the trigger to the first button inside the popover. By pressing tab repeatedly, you can move from button to button until you finally reach the next button outside the popover. <p> <button popovertarget="popover-buttons">First Button</button> <button>Second Button</button> </p> <div popover id="popover-buttons"> <button>Focusable</button> <button>Focusable</button> <button>Focusable</button> </div> First Button Second Button Focusable Focusable Focusable That works as long as you don't use slots or the details element inside your popovers. If you do, focus will still move from the trigger to the first button inside the popover, but if you press Enter, focus doesn't jump to the next focusable element inside the popover; it skips all remaining elements, leaves the popover, and then jumps to the next button outside the

## How CodeTV built a video streaming platform with Astro and Mux

DevFeed: [How CodeTV built a video streaming platform with Astro and Mux](<https://devfeed.tech/articles/unleashing-creativity-3396.md>)

Original publisher: [Read original article](<https://astro.build/case-studies/codetv/>)

Published: 2025-09-09T00:00:00Z

Content type: article

Language: en

Sources: [The Astro Blog](<https://devfeed.tech/sources/the-astro-blog.md>)

Topics: [Astro](<https://devfeed.tech/topics/astro.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Website](<https://devfeed.tech/topics/website.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [data-architecture](<https://devfeed.tech/topics/data-architecture.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Content Management System](<https://devfeed.tech/topics/cms.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [astro](<https://devfeed.tech/tags/astro.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automation](<https://devfeed.tech/tags/automation.md>), [cms](<https://devfeed.tech/tags/cms.md>), [developers](<https://devfeed.tech/tags/developers.md>), [performance](<https://devfeed.tech/tags/performance.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

This case study explains how CodeTV used Astro and Mux to build a subscription-based video streaming platform for developer programming. It describes the platform's requirements, including content management, authentication, e-commerce, asset management, search, workflow automation, and adaptive-bitrate video streaming.

### Source excerpt

How CodeTV built a video streaming platform with Astro and Mux

## Launching MDN's new front end

DevFeed: [Launching MDN's new front end](<https://devfeed.tech/articles/launching-mdn-s-new-front-end-4086.md>)

Original publisher: [Read original article](<https://developer.mozilla.org/en-US/blog/launching-new-front-end/>)

Author: mdn-team

Published: 2025-08-19T00:00:00Z

Content type: article

Language: en

Sources: [MDN Blog](<https://devfeed.tech/sources/mdn-blog.md>)

Topics: [Front end](<https://devfeed.tech/topics/frontend.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [CSS](<https://devfeed.tech/topics/css.md>), [Web APIs](<https://devfeed.tech/topics/web-apis.md>), [HTML](<https://devfeed.tech/topics/html.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Usability](<https://devfeed.tech/topics/usability.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [code](<https://devfeed.tech/tags/code.md>), [components](<https://devfeed.tech/tags/components.md>), [css](<https://devfeed.tech/tags/css.md>), [developers](<https://devfeed.tech/tags/developers.md>), [front-end](<https://devfeed.tech/tags/front-end.md>), [github](<https://devfeed.tech/tags/github.md>), [library](<https://devfeed.tech/tags/library.md>), [ui](<https://devfeed.tech/tags/ui.md>), [usability](<https://devfeed.tech/tags/usability.md>), [web](<https://devfeed.tech/tags/web.md>), [web-apis](<https://devfeed.tech/tags/web-apis.md>)

### AI overview

MDN has launched a rebuilt front end with a cleaner interface, improved usability, and support for modern CSS and web components. The update also improves typography, code rendering, search, icons, and navigation.

### Source excerpt

MDN is getting a facelift 🎉. Discover what's changed, what's improved, and how navigating the site just got smoother.

## Bluesky Likes Web Components

DevFeed: [Bluesky Likes Web Components](<https://devfeed.tech/articles/bluesky-likes-web-components-52161.md>)

Original publisher: [Read original article](<https://lea.verou.me/blog/2025/bluesky-likes/>)

Author: Lea Verou

Published: 2025-06-17T00:00:00Z

Content type: article

Language: en

Sources: [Lea Verou's blog](<https://devfeed.tech/sources/lea-verou-s-blog.md>)

Topics: [Web Components](<https://devfeed.tech/topics/web-components.md>), [API](<https://devfeed.tech/topics/api.md>), [Bluesky](<https://devfeed.tech/topics/bluesky-social.md>), [Web](<https://devfeed.tech/topics/web.md>)

Tags: [a11y](<https://devfeed.tech/tags/a11y.md>), [api](<https://devfeed.tech/tags/api.md>), [api-design](<https://devfeed.tech/tags/api-design.md>), [article](<https://devfeed.tech/tags/article.md>), [blog](<https://devfeed.tech/tags/blog.md>), [bluesky](<https://devfeed.tech/tags/bluesky.md>), [components](<https://devfeed.tech/tags/components.md>), [i18n](<https://devfeed.tech/tags/i18n.md>), [launch](<https://devfeed.tech/tags/launch.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [web-components](<https://devfeed.tech/tags/web-components.md>), [web-standards](<https://devfeed.tech/tags/web-standards.md>)

### AI overview

The author presents web components for displaying Bluesky post likes and discusses the practical challenges of building accessible, localizable components that consume public API data. The article highlights Bluesky's open API, which allows unauthenticated access to public data without an API key.

### Source excerpt

Just want the components? Here you go: Demo Repo NPM A love letter to the Bluesky API I'm old enough to remember the golden Web 2.0 era, when many of today's big social media platforms grew up. A simpler time, when the Web was much more extroverted. It was common for websites to embed data from others (the peak of mashups), and prominently feature widgets from various platforms to showcase a post's likes or shares. Especially Twitter was so ubiquitous that the number of Twitter shares was my primary metric for how much people were interested in a blog post I wrote. Then, websites started progressively becoming walled gardens, guarding their data with more fervor than Gollum guarding the Precious. Features disappeared or got locked behind API keys, ridiculous rate limits, expensive paywalls, and other restrictions. Don't get me wrong, I get it. A lot of it was reactionary, a response to abuse -- the usual reason we can't have nice things. And even when it was to stimulate profit -- it is understandable that they want to monetize their platforms. People gotta eat. I was recently reading this interesting article by Salma Alam-Naylor. The article makes some great points, but it was something else that caught my eye: the widget of Bluesky likes at the bottom. Salma's Bluesky likes widget that inspired these I mentioned it to my trusty apprentice Dmitry who discovered the API was actually much simpler than what we've come to expect. Later, it turned out Salma has even written an entire post on how to implement the same thing on your own site. The openness of the API was so refreshing. Not only can you read public data without being authenticated, you don't even need an API key! Major nostalgia vibes. It seemed the perfect candidate for a web component that you can just drop in to a page, give it a post URL, and it will display the likes for that post. I just had to make it, and of course use it right here. Web Components that use API data have been historically awkward. Let

## Using Rails Views, Web Components, React, and Rails ViewComponents Together

DevFeed: [Using Rails Views, Web Components, React, and Rails ViewComponents Together](<https://devfeed.tech/articles/rails-views-web-components-react-why-make-a-choice-33528.md>)

Original publisher: [Read original article](<https://www.aha.io/engineering/articles/rails-views-web-components-react>)

Published: 2025-03-03T00:00:00Z

Content type: opinion

Language: en

Sources: [Aha! Engineering Blog](<https://devfeed.tech/sources/aha-engineering-blog.md>)

Topics: [Ruby on Rails](<https://devfeed.tech/topics/ruby-on-rails.md>), [React](<https://devfeed.tech/topics/react.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Server-side rendering](<https://devfeed.tech/topics/server-side-rendering.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [vendor lock-in](<https://devfeed.tech/topics/vendor-lock-in.md>)

Tags: [components](<https://devfeed.tech/tags/components.md>), [front-end](<https://devfeed.tech/tags/front-end.md>), [opinion](<https://devfeed.tech/tags/opinion.md>), [rails](<https://devfeed.tech/tags/rails.md>), [react](<https://devfeed.tech/tags/react.md>), [server-side-rendering](<https://devfeed.tech/tags/server-side-rendering.md>), [vendor-lock-in](<https://devfeed.tech/tags/vendor-lock-in.md>)

### AI overview

The article argues that Rails views, web components, React, and Rails ViewComponents are not mutually exclusive. It explains that each approach addresses different problems and can be combined thoughtfully, including server rendering for simpler data-display features and web components for avoiding vendor lock-in.

### Source excerpt

How many times have you heard or read statements like these in tech discussions?"Everything needs to be a single-page app these days. Server-rendered templates are holding you back.""Web components are the future. Why tie yourself to any framework?"

## Bringing Signals to Lit Labs

DevFeed: [Bringing Signals to Lit Labs](<https://devfeed.tech/articles/bringing-signals-to-lit-labs-3523.md>)

Original publisher: [Read original article](<https://lit.dev/blog/2024-10-08-signals/>)

Author: Lit Team

Published: 2024-10-08T00:00:00Z

Content type: release

Language: en

Sources: [Lit Blog](<https://devfeed.tech/sources/lit-blog.md>)

Topics: [JavaScript](<https://devfeed.tech/topics/javascript.md>), [reactive](<https://devfeed.tech/topics/reactive.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [polyfill](<https://devfeed.tech/topics/polyfill.md>)

Tags: [compatibility](<https://devfeed.tech/tags/compatibility.md>), [components](<https://devfeed.tech/tags/components.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [polyfill](<https://devfeed.tech/tags/polyfill.md>), [reactive](<https://devfeed.tech/tags/reactive.md>)

### AI overview

Lit Labs announced @lit-labs/signals, a package that integrates the polyfill for the TC39 Signals proposal with Lit. It enables shared observable signals for reactive state management, automatic component updates, targeted re-renders, and interoperability across libraries and frameworks.

### Source excerpt

The new Signals package integrates the TC39 Signals proposal with Lit

## Web Components are not Framework Components -- and That's Okay

DevFeed: [Web Components are not Framework Components -- and That's Okay](<https://devfeed.tech/articles/web-components-are-not-framework-components-and-that-s-okay-52160.md>)

Original publisher: [Read original article](<https://lea.verou.me/blog/2024/wcs-vs-frameworks/>)

Author: Lea Verou

Published: 2024-10-01T00:00:00Z

Content type: opinion

Language: en

Sources: [Lea Verou's blog](<https://devfeed.tech/sources/lea-verou-s-blog.md>)

Topics: [Web Components](<https://devfeed.tech/topics/web-components.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [web-standards](<https://devfeed.tech/topics/web-standards.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [blog](<https://devfeed.tech/tags/blog.md>), [components](<https://devfeed.tech/tags/components.md>), [framework](<https://devfeed.tech/tags/framework.md>), [standards](<https://devfeed.tech/tags/standards.md>), [web](<https://devfeed.tech/tags/web.md>), [web-components](<https://devfeed.tech/tags/web-components.md>), [web-platform](<https://devfeed.tech/tags/web-platform.md>), [web-standards](<https://devfeed.tech/tags/web-standards.md>)

### AI overview

The author argues that Web Components and framework components serve different purposes, and that Web Components should be evaluated against the long-term requirements of the web platform rather than only against current userland frameworks. The post discusses durability, backward compatibility, accessibility, internationalization, and distributed standards work.

### Source excerpt

Disclaimer: This post expresses my opinions, which do not necessarily reflect consensus by the whole Web Components community. A blog post by Ryan Carniato titled "Web Components Are Not the Future" has recently stirred a lot of controversy. A few other JS framework authors pitched in, expressing frustration and disillusionment around Web Components. Some Web Components folks wrote rebuttals, while others repeatedly tried to get to the bottom of the issues, so they could be addressed in the future. When you are on the receiving end of such an onslaught, the initial reaction is to feel threatened and become defensive. However, these kinds of posts can often end up shaking things up and pushing a technology forwards in the end. I have some personal experience: after I published my 2020 post titled "The failed promise of Web Components" which also made the rounds at the time, I was approached by a bunch of folks (Justin Fagnani, Gray Norton, Kevin Schaaf) about teaming up to fix the issues I described. The result of these brainstorming sessions was the Web Components CG which now has a life of its own and has become a vibrant Web Components community that has helped move several specs of strategic importance forwards. As someone who deeply cares about Web Components, my initial response was also to push back. I was reminded of how many times I have seen this pattern before. It is common for new web platform features to face pushback and resistance for many years; we tend to compare them to current userland practices, and their ergonomics often fare poorly at the start. Especially when there is no immediately apparent 80/20 solution, making things possible tends to precede making them easy. Web platform features operate under a whole different set of requirements and constraints: They need to last decades, not just until the next major release. They need to not only cater to the current version of the web platform, but anticipate its future evolution and be compatible w

## Joining Font Awesome as Product Lead to Improve Web UI Products and Standards

DevFeed: [Joining Font Awesome as Product Lead to Improve Web UI Products and Standards](<https://devfeed.tech/articles/making-the-web-more-awesome-for-everyone-52154.md>)

Original publisher: [Read original article](<https://lea.verou.me/blog/2024/awesome/>)

Author: Lea Verou

Published: 2024-09-16T00:00:00Z

Content type: opinion

Language: en

Sources: [Lea Verou's blog](<https://devfeed.tech/sources/lea-verou-s-blog.md>)

Topics: [Web](<https://devfeed.tech/topics/web.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [Usability](<https://devfeed.tech/topics/usability.md>), [web-standards](<https://devfeed.tech/topics/web-standards.md>), [Icon font](<https://devfeed.tech/topics/icon-font.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [blog](<https://devfeed.tech/tags/blog.md>), [css](<https://devfeed.tech/tags/css.md>), [design](<https://devfeed.tech/tags/design.md>), [font-awesome](<https://devfeed.tech/tags/font-awesome.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [personal](<https://devfeed.tech/tags/personal.md>), [product](<https://devfeed.tech/tags/product.md>), [ui](<https://devfeed.tech/tags/ui.md>), [usability](<https://devfeed.tech/tags/usability.md>), [web-awesome](<https://devfeed.tech/tags/web-awesome.md>), [web-components](<https://devfeed.tech/tags/web-components.md>), [web-platform](<https://devfeed.tech/tags/web-platform.md>), [web-standards](<https://devfeed.tech/tags/web-standards.md>)

### AI overview

The author announces joining Font Awesome as Product Lead after completing a PhD focused on usability and programming language design. The role involves improving product design and usability, developing Web Awesome with web components and CSS, and contributing web platform pain points to standards proposals.

### Source excerpt

Folks, I have some exciting news to share. 🤩 Today I start a new chapter in my career. After a decade at MIT, teaching and doing research at the intersection of usability and programming language design, I wrapped up my PhD two weeks ago (yes, I'm a Dr now! And damn right I will -- once it actually sinks in) and today I start my new role as Product Lead at Font Awesome. I will be evaluating user needs and improving product design and usability across all company products, with an emphasis on Web Awesome, the product we are launching early next year to revolutionize how Web UIs are built by using web components and CSS in ways you've never seen before. Beyond improving the products themselves (all of which include extensive free & open source versions), part of my role will utilize my web standards experience to collect web platform pain points from across the company and translating them to new and existing web standards proposals. Yes, I know, it's a match made in heaven. 😍 There is even a small chance I may have been the first to create an icon font for use in a web UI via @font-face, which would make it even more wonderfully poetic that I'm joining the company that has become synonymous with icon fonts on the Web. However, it was not my MIT PhD that led me to this role, but an email from Dave Gandy (creator & CEO of Font Awesome) about Color.js, that turned into hours of chats, and eventually a job offer for a role I could not refuse, one that was literally molded around my skills and interests. The role is not the only reason I'm excited to join Font Awesome, though. The company itself is a breath of fresh air: open source friendly (as Dave says, "literally the only reason we have Pro versions is that we need to sustain this somehow" 😅), already profitable (= no scrambling to meet VC demands by cramming AI features nobody wants into our products), fully remote, huge emphasis on work-life balance, and an interview process that did not feel like an interview -- or e

[Next page](<https://devfeed.tech/topics/web-components.md?cursor=WyIyMDI0LTA5LTE2VDAwOjAwOjAwKzAwOjAwIiwgIjRjZmFkOTdjLWQ0MmMtNDlhYy05NGQwLTQ1NTg5ZTcwNTU0NiJd>)