Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Administered by:

Server stats:

506
active users

101010.pl: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.0-beta.1

#webcomponent

0 posts0 participants0 posts today
*
Tane Piper ⁂

I think I've accidentally built quite a cool '#webComponent-as-a-plugin' system for the @teskooano UI - essentially two functions - one to register base components, and one to register full plugins, that are made up of one or more web components, functions and a controller. These components can self-register things like buttons in certain toolbars, or you can just add them as functions (like opening a new external URL). I'll post a bit more on it later

Dave Copeland :ruby:

#TIL, (and I cannot find documented), but can easily replicate is that when a #WebComponent #CustomElement's `connectedCallback()` is called, `innerHTML` is undefined, UNLESS, you wait to define your custom element after DOMContentLoaded.

I wish there was a callback for a custom element that amounted to “the element has been loaded", but I can see that this doesn't necessarily make sense.

[Can't recreate in codepen since it runs all stuff after DOM loaded.]

gist.github.com/davetron5000/2

Mia (web luddite)

Anyone know of an existing #WebComponent that does audio playlist progressive enhancement, something like this?

<play-list>
<audio-track>
<track-name for="track-1">My Track</track-name>
<audio controls id="track-1" src="…">
</audio-track>
…
</play-list>

(I haven't considered all the details here, just sketching. Should default to individual audio elements with browser UI, but add play-all features on top of that?)

ExploreLive feeds
About