#lightDOM

Inautiloinautilo
2024-12-12


Isomorphic web components · Who says web components can’t be rendered server-side? ilo.im/161cdx

_____

Inautiloinautilo
2024-11-21


Combining light DOM and shadow DOM · How to mix-and-match both in a web component ilo.im/160yn2

_____

pablolarahpablolarah
2024-11-19

🟣 Combining light DOM and shadow DOM in a Web Component

by @cferdinandi.bsky.social

gomakethings.com/combining-lig

Violet illustration of man with umbrella and hat projecting a shadow that looks like his carrying a person. 
Violet text: Combining light DOM and shadow DOM in a Web Component
Inautiloinautilo
2024-08-07
Inautiloinautilo
2024-06-17


Web components without jumping from 0 to 100 · How you can start small with custom HTML elements ilo.im/15z83x

_____

Inautiloinautilo
2024-01-05


Shadow DOM and the problem of encapsulation · Shadow DOM’s accomplishment in web components ilo.im/15xjkz

_____

Inautiloinautilo
2023-12-27


Shadow DOM is for hiding your shame · Light DOM is for the ideal, perfect structure. ilo.im/15i68u

_____

2023-12-06

"With a traditional HTML component, any developer who uses it will need to update their HTML, JavaScript, and CSS files to include the fix. With web components, they only have to update the JavaScript file."

htmhell.dev/adventcalendar/202

Very straightforward #WebComponents example by @cferdinandi by showing how to create the (classic?) counter button.

#HTML #JavaScript #WebDev #Frontend #ShadowDOM #LightDOM

2023-11-10

🌤️ Head Toward the Light DOM

Recently, there has been a spate of articles that talk about using the Light DOM in Web Components. Everyone knows we are extremely pro-Light DOM web components. Today, we are announcing some new client-side Light DOM functionality.

by @macdonst

#webcomponents #lightdom

begin.com/blog/posts/2023-11-1

2023-10-25

`aria-labelledby` and `aria-describedby` attributes requiring IDs is but a one example of #accessibility being unaccessible to the dev like me. Only do you get a conflict in IDs for #ARIA and browser will choose to silently fail with the first occurence of element ID. Couldn't those be scoped CSS #selectors to actually make sense? I cannot willingly drag my hand and implant unique IDs on a whim: first thing, I have to come up with really witty names, another - mangle the markup of reusable component... wait.

Now that I think about it, maybe that's one superior use for #ShadowDOM over #LightDOM? Are #CustomElements getting more compatible with #a11y things with months to come? I wanna employ #WebComponents in #Kbin fork, but I need a strong reasoning for this.

2022-12-01

@kulykov I finalized boilerplate in base class. Type hints are asinine, albeit logic for slot update takes into account:
+ addedNodes (additions to the #LightDOM),
+ removedNodes (nodes previously assigned to slots now trigger callback for each of the same slots to handle fallback),
+ target (text changes within those nodes).

Was stuck doing UserCard component. It can now accept user's name and email via slots, and update name initials in the inner Avatar based on slot text.

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst