cc @Una @argyleink
=> More informations about this toot | View the thread
[#]CSS smart folks, I need help 🥺
I'm using anchor positioning to show a popover as a tooltip but I can't figure out how to make the little triangle move around when a position-try
fallback is used.
Is there a way to modify ::after
pseudo-element when a @position-try
fallback is used? Even some JS api to detect a change in position-area
or even just a change in top
?
Note: MutationObserver doesn't work because the DOM isn't changing when a fallback is used.
WIP codepen is at https://codepen.io/wes_goulet/pen/GRVgyGq
=> More informations about this toot | View the thread
@eleventy Figured out a workaround for now. Still no type-checking/autocomplete in the template code, but at least the setup code has type checking and my component API is defined. Baby steps.
=> More informations about this toot | View the thread
@eleventy Actually, this isn't working because it seems like I can't access the component properties in the webc:setup script.
https://github.com/11ty/webc/issues/196
=> More informations about this toot | View the thread
@eleventy I really just want a way to define my component API when authoring components so when I come back to the component it's clear what the contract is without looking through the component's HTML.
=> More informations about this toot | View the thread
Trying to bring some type-checking to webc components in @eleventy via #jsdoc comments
=> More informations about this toot | View the thread
@eleventy I’m using webc and really like the idea of build-time web components.
Hopefully there will eventually be a vscode plugin to make the DX a bit nicer, writing JS in attribute strings isn’t my fave but it gets the job done.
=> More informations about this toot | View the thread
Been working on fandwagon the past few nights.
Pure static site, built with
@eleventy 💪
Zero client side JavaScript so far… that’ll come soon (stuff like locale aware times), just trying to get a good baseline experience to start from and then progressive enhance from there.
=> More informations about this toot | View the thread
I think the vscode #typescript plugin needs an update to support the new jsdoc @import
syntax.
In the screenshot line 4 (the type import line) is grayed out because it thinks it's unused, but it's used on line 9
=> More informations about this toot | View the thread
=> This profile with reblog | Go to goulet@techhub.social account This content has been proxied by September (3851b).Proxy Information
text/gemini