# Scoped custom element registries end tag clashes

Source: [DEV Community: javascript](https://dev.to/richicodes/scoped-custom-element-registries-end-tag-clashes-bm0) · 2026-11-11 · Frontend
Page: https://themorning.dev/story/scoped-custom-element-registries-end-tag-clashes-4333aea7dd327bcb
Kind: release · Impact: medium

## In brief

- Scoped custom element registries let two libraries define the same custom element name on one page without breaking each other.
- The feature became Baseline on 27 October 2026, when Firefox 159 shipped it.
- Chrome and Edge 146 are also named in the source as supporting the feature.

## Why it matters

Developers combining several component libraries on one page can avoid tag name collisions that previously broke one of them.

## Versions

- Firefox 159
- Chrome 146
- Edge 146

## Timeline

- 2026-10-27: Scoped custom element registries became Baseline when Firefox 159 shipped them

## Coverage

- [Scoped custom element registries end tag clashes](https://dev.to/richicodes/scoped-custom-element-registries-end-tag-clashes-bm0) — DEV Community: javascript, 2026-11-11

Tags: web components, custom elements, browsers, baseline, javascript

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev