FrontEnd Engineering Explained is live - ShadowDOM, Transforms, CommandFor, And The Matrix - Featuring @bram.us @stefanmatei.com @bell.bz @nicolesullivan.bsky.social @kilianvalkhof.com @cassidoo.co @zachleat.com @lea.verou.me #webdev 🙌✌️🤘
frontend-engineering-explained.kit.com/posts/fronte...
frontend-engineering-explained.kit.com/posts/fronte...
FrontEnd Engineering Explained - ShadowDOM, Transforms, CommandFor And The Matrix
frontend-engineering-explained.kit.com
February 23, 2025 at 7:12 PM
FrontEnd Engineering Explained is live - ShadowDOM, Transforms, CommandFor, And The Matrix - Featuring @bram.us @stefanmatei.com @bell.bz @nicolesullivan.bsky.social @kilianvalkhof.com @cassidoo.co @zachleat.com @lea.verou.me #webdev 🙌✌️🤘
frontend-engineering-explained.kit.com/posts/fronte...
frontend-engineering-explained.kit.com/posts/fronte...
undertale if it were Web.
papyrus: welcome to the shadowDOM
sans: how was the crawl
papyrus: welcome to the shadowDOM
sans: how was the crawl
March 3, 2025 at 2:11 PM
undertale if it were Web.
papyrus: welcome to the shadowDOM
sans: how was the crawl
papyrus: welcome to the shadowDOM
sans: how was the crawl
today's rabbithole: learning that Safari continues to break #accessibility with display:contents.
i found (on a production site!) that VoiceOver completely skips over nested display:contents elements inside shadowDOM.
bug report (kindly opened by @knowler.dev): bugs.webkit.org/show_bug.cgi...
i found (on a production site!) that VoiceOver completely skips over nested display:contents elements inside shadowDOM.
bug report (kindly opened by @knowler.dev): bugs.webkit.org/show_bug.cgi...
Safari nested display:contents + shadow DOM bug
...
codepen.io
November 21, 2024 at 8:19 PM
today's rabbithole: learning that Safari continues to break #accessibility with display:contents.
i found (on a production site!) that VoiceOver completely skips over nested display:contents elements inside shadowDOM.
bug report (kindly opened by @knowler.dev): bugs.webkit.org/show_bug.cgi...
i found (on a production site!) that VoiceOver completely skips over nested display:contents elements inside shadowDOM.
bug report (kindly opened by @knowler.dev): bugs.webkit.org/show_bug.cgi...
As @lukewarlow.dev pointed out on Mastodon, the :has() solution wouldn't work with ShadowDOM.
June 23, 2026 at 9:46 AM
As @lukewarlow.dev pointed out on Mastodon, the :has() solution wouldn't work with ShadowDOM.
Struggling with screen readers ignoring your Shadow DOM components? Learn how the accessibility tree works and practical fixes like delegatesFocus and ARIA roles to bridge the gap. Make your web components truly accessible. #Accessibility #ShadowDOM #WebComponents #ScreenReaders https://blog.mspk.me
September 21, 2026 at 10:48 AM
Struggling with screen readers ignoring your Shadow DOM components? Learn how the accessibility tree works and practical fixes like delegatesFocus and ARIA roles to bridge the gap. Make your web components truly accessible. #Accessibility #ShadowDOM #WebComponents #ScreenReaders https://blog.mspk.me
WC Review:
Like:
- exposing functions is easy
- devtools integration is 🔥
- mental model relatively simple
- @lit.dev is lit
No Like:
- ShadowDom
- having to rely on lifecycle methods rather than render functions
- High barrier to local reasoning/state
Like:
- exposing functions is easy
- devtools integration is 🔥
- mental model relatively simple
- @lit.dev is lit
No Like:
- ShadowDom
- having to rely on lifecycle methods rather than render functions
- High barrier to local reasoning/state
May 11, 2025 at 8:41 PM
WC Review:
Like:
- exposing functions is easy
- devtools integration is 🔥
- mental model relatively simple
- @lit.dev is lit
No Like:
- ShadowDom
- having to rely on lifecycle methods rather than render functions
- High barrier to local reasoning/state
Like:
- exposing functions is easy
- devtools integration is 🔥
- mental model relatively simple
- @lit.dev is lit
No Like:
- ShadowDom
- having to rely on lifecycle methods rather than render functions
- High barrier to local reasoning/state
FYI: I (and others before me) found a bug in Chromium where elements in ShadowDOM inside a popover can't be focused.
codepen.io/matuzo/pen/R...
issues.chromium.org/issues/40228...
codepen.io/matuzo/pen/R...
issues.chromium.org/issues/40228...
ShadowDOM popover bug
...
codepen.io
November 12, 2025 at 1:37 PM
FYI: I (and others before me) found a bug in Chromium where elements in ShadowDOM inside a popover can't be focused.
codepen.io/matuzo/pen/R...
issues.chromium.org/issues/40228...
codepen.io/matuzo/pen/R...
issues.chromium.org/issues/40228...
Shadowverse implies the existence of Shadowdom and Shadowsub
June 20, 2025 at 3:56 PM
Shadowverse implies the existence of Shadowdom and Shadowsub
How I use Web Components with ShadowDOM in a Design System. www.ethangardner.com/posts/shadow...
How I Use ShadowDOM with Web Components in Design Systems
Web components and CSS custom properties can create a future-proof design system with maximum flexibility
www.ethangardner.com
January 30, 2026 at 7:07 PM
How I use Web Components with ShadowDOM in a Design System. www.ethangardner.com/posts/shadow...
And the fun starts when you used:
:not:defined { display: none }
to prevent FOUCs or any other weird reason.
Because DSD - Declarative ShadowDOM
creates *undefined* Custom Elements
The Custom Elements JavaScript *API* makes them :defined
:not:defined { display: none }
to prevent FOUCs or any other weird reason.
Because DSD - Declarative ShadowDOM
creates *undefined* Custom Elements
The Custom Elements JavaScript *API* makes them :defined
September 25, 2026 at 5:22 PM
And the fun starts when you used:
:not:defined { display: none }
to prevent FOUCs or any other weird reason.
Because DSD - Declarative ShadowDOM
creates *undefined* Custom Elements
The Custom Elements JavaScript *API* makes them :defined
:not:defined { display: none }
to prevent FOUCs or any other weird reason.
Because DSD - Declarative ShadowDOM
creates *undefined* Custom Elements
The Custom Elements JavaScript *API* makes them :defined
I still dream of an entirely Web Component-based version of SB. Less DIV-itis in the UI layer for story debugging. The style isolation of ShadowDOM would be good, especially for a product that shows other people's code and styles. But. I'm content with the other perf improvments for now.
September 9, 2025 at 4:48 PM
I still dream of an entirely Web Component-based version of SB. Less DIV-itis in the UI layer for story debugging. The style isolation of ShadowDOM would be good, especially for a product that shows other people's code and styles. But. I'm content with the other perf improvments for now.
ppl believing/being sold the ShadowDOM as a default when the web is lightdom by default is the problem. SD is useful in very narrow use cases and a massive burden of tradeoffs if yagni.
March 13, 2026 at 6:27 PM
ppl believing/being sold the ShadowDOM as a default when the web is lightdom by default is the problem. SD is useful in very narrow use cases and a massive burden of tradeoffs if yagni.
LavaDome is the newest experimental tool in the LavaMoat toolbox for supply chain security, using the ShadowDom web API.
June 6, 2024 at 1:16 PM
LavaDome is the newest experimental tool in the LavaMoat toolbox for supply chain security, using the ShadowDom web API.
Servo Weekly Report Nº 19
Highlights from the last week:
• Continued progress to implement ShadowDOM
• Continued Flexbox improvements
• Add ReferrerPolicy IDL attribute to iframes
• Upgraded Stylo to 2024-12-04
1/2
Highlights from the last week:
• Continued progress to implement ShadowDOM
• Continued Flexbox improvements
• Add ReferrerPolicy IDL attribute to iframes
• Upgraded Stylo to 2024-12-04
1/2
Servo - Open Collective
The embeddable, independent, memory-safe, modular, parallel web rendering engine. For more details on fees, go to https://servo.org/sponsorship/#donation-fees
opencollective.com
December 11, 2024 at 1:20 PM
Servo Weekly Report Nº 19
Highlights from the last week:
• Continued progress to implement ShadowDOM
• Continued Flexbox improvements
• Add ReferrerPolicy IDL attribute to iframes
• Upgraded Stylo to 2024-12-04
1/2
Highlights from the last week:
• Continued progress to implement ShadowDOM
• Continued Flexbox improvements
• Add ReferrerPolicy IDL attribute to iframes
• Upgraded Stylo to 2024-12-04
1/2
Everytime I need shadowDOM, it is for scoped HTML first, CSS second
Would be great if the browser could create variables from IDs in shadowDOM (on the Custom Element) like it does with "global" IDs (thank you Microsoft in 1996) saving us from typing querySelector / getElementById
Would be great if the browser could create variables from IDs in shadowDOM (on the Custom Element) like it does with "global" IDs (thank you Microsoft in 1996) saving us from typing querySelector / getElementById
July 16, 2025 at 7:07 PM
Everytime I need shadowDOM, it is for scoped HTML first, CSS second
Would be great if the browser could create variables from IDs in shadowDOM (on the Custom Element) like it does with "global" IDs (thank you Microsoft in 1996) saving us from typing querySelector / getElementById
Would be great if the browser could create variables from IDs in shadowDOM (on the Custom Element) like it does with "global" IDs (thank you Microsoft in 1996) saving us from typing querySelector / getElementById
oh no i just got lost in the shadowdom
January 29, 2026 at 2:55 AM
oh no i just got lost in the shadowdom
The new release of "Blazor HotKeys 2" has been rolled out!
github.com/jsakamoto/To...
Excluding now will work better even if an element is inside a shadowDOM. This change improves hotkey behavior on some UI component libraries, such as Fluent UI Blazor. #Blazor
github.com/jsakamoto/To...
Excluding now will work better even if an element is inside a shadowDOM. This change improves hotkey behavior on some UI component libraries, such as Fluent UI Blazor. #Blazor
December 19, 2024 at 9:32 AM
The new release of "Blazor HotKeys 2" has been rolled out!
github.com/jsakamoto/To...
Excluding now will work better even if an element is inside a shadowDOM. This change improves hotkey behavior on some UI component libraries, such as Fluent UI Blazor. #Blazor
github.com/jsakamoto/To...
Excluding now will work better even if an element is inside a shadowDOM. This change improves hotkey behavior on some UI component libraries, such as Fluent UI Blazor. #Blazor
Wtf is #shadowdom and can it please go away?
February 22, 2025 at 7:45 PM
Wtf is #shadowdom and can it please go away?
Here it is: bugs.webkit.org/show_bug.cgi...
269717 – CSSStyleSheets don't invalidate properly inside ShadowDOM
bugs.webkit.org
June 26, 2026 at 1:18 PM
Here it is: bugs.webkit.org/show_bug.cgi...
Naming is hard
I teach there are UNDefined and Defined Custom Elements
I didn't include shadowDOM because it can be set on Native and Custom Elements
But not on Unknown Elements
DSD-Declarative ShadowDOM IS a UNDefined Custom Element
I call a Native Element + shadowDOM a Web Component too
I teach there are UNDefined and Defined Custom Elements
I didn't include shadowDOM because it can be set on Native and Custom Elements
But not on Unknown Elements
DSD-Declarative ShadowDOM IS a UNDefined Custom Element
I call a Native Element + shadowDOM a Web Component too
May 26, 2026 at 6:33 AM
Naming is hard
I teach there are UNDefined and Defined Custom Elements
I didn't include shadowDOM because it can be set on Native and Custom Elements
But not on Unknown Elements
DSD-Declarative ShadowDOM IS a UNDefined Custom Element
I call a Native Element + shadowDOM a Web Component too
I teach there are UNDefined and Defined Custom Elements
I didn't include shadowDOM because it can be set on Native and Custom Elements
But not on Unknown Elements
DSD-Declarative ShadowDOM IS a UNDefined Custom Element
I call a Native Element + shadowDOM a Web Component too
I seriously don't understand how people have so many problems with ShadowDOM.
Unless they try to do things it specifically prevents you from doing.
Unless they try to do things it specifically prevents you from doing.
March 31, 2025 at 11:45 AM
I seriously don't understand how people have so many problems with ShadowDOM.
Unless they try to do things it specifically prevents you from doing.
Unless they try to do things it specifically prevents you from doing.
I’ll give a short talk tomorrow at Factorial.io about Declarative ShadowDOM. It lets us use web components and ShadowDOM even with server-side rendering and SSG environments like @astro.build. I recorded a practice run on YouTube for you to check out: www.youtube.com/watch?v=m2FF... #webdev
Exploring Declarative Shadow DOM - Frontend Engineering Explained #webdevelopment
YouTube video by Schalk Neethling
www.youtube.com
February 19, 2025 at 8:17 PM
I’ll give a short talk tomorrow at Factorial.io about Declarative ShadowDOM. It lets us use web components and ShadowDOM even with server-side rendering and SSG environments like @astro.build. I recorded a practice run on YouTube for you to check out: www.youtube.com/watch?v=m2FF... #webdev
Shadow DOM is like the dark side of the moon for me.
Fixing drag events 🥸
Does anybody know a great DnD lib for react.js or vanilla?
#buildinpublic #javascript #shadowdom
Fixing drag events 🥸
Does anybody know a great DnD lib for react.js or vanilla?
#buildinpublic #javascript #shadowdom
January 31, 2025 at 10:58 AM
Shadow DOM is like the dark side of the moon for me.
Fixing drag events 🥸
Does anybody know a great DnD lib for react.js or vanilla?
#buildinpublic #javascript #shadowdom
Fixing drag events 🥸
Does anybody know a great DnD lib for react.js or vanilla?
#buildinpublic #javascript #shadowdom
shadowDOMにlabelのid配って参照できるやつshipされたんだ
June 24, 2026 at 12:26 AM
shadowDOMにlabelのid配って参照できるやつshipされたんだ