| Blog | https://coryrylan.com |
| GitHub | https://github.com/coryrylan |
| Web Components | https://webcomponent.dev |
| Angular Forms | https://angularforms.dev |
| Blog | https://coryrylan.com |
| GitHub | https://github.com/coryrylan |
| Web Components | https://webcomponent.dev |
| Angular Forms | https://angularforms.dev |
Who likes themselves some #webComponents related #interop2024 proposals?
+1 them while they are hot!
Reference Target: https://github.com/web-platform-tests/interop/issues/792
:host(:has(...)) and :host:has(...): https://github.com/web-platform-tests/interop/issues/791
:has-slotted: https://github.com/web-platform-tests/interop/issues/790
Import Attributes: https://github.com/web-platform-tests/interop/issues/733
CSS Module Scripts: https://github.com/web-platform-tests/interop/issues/703
It's gonna be a good year!
TC39 [update: will be] discussing making a #JavaScript compile step part of the standard.
I don’t think that’s a good idea, I don’t think I’m alone in that, but I fear we might be too few.
Please don’t break the web (even more).
https://toot.cafe/@tomayac/113259678138456511
From the agenda for the 104th meeting of Ecma #TC39 (https://github.com/tc39/agendas/blob/main/2024/10.md#agenda-items). Longer or open-ended discussions: JSSugar/JS0: https://docs.google.com/presentation/d/1ylROTu3N6MyHzNzWJXQAc7Bo1O0FHO3lNKfQMfPOA4o/mobilepresent?slide=id.g30432c5cd9c_0_688. Slide 40 onward 👀: Let's standardize as the ecosystem uses it: JS0: the language implemented by the engines JSSugar: features that must be compiled by tools to JS0 For developers, JS = #JS0 + #JSSugar
Comparing web components to React is like comparing a good bicycle with a cybertruck.
They do very different things, and they’re used by different people with very, very different mindsets.
Flow Charts with CSS Anchor Positioning
https://coryrylan.com/blog/flow-charts-with-css-anchor-positioning
@jensimmons A CSS Feature I have longed for is a complete implementation of the `attr(name type)` in CSS properties other than `content`.
Usually, I just want to set colors, percents, or background or mask image URLs.
Example: changing / animating the background color on a <meter> depending on the `value` attribute required I make 20+ rules to roughly parse the value attribute, when with attr could have done it one rule.
Reference: https://drafts.csswg.org/css-values-5/#funcdef-attr
@slightlyoff I am basically at the point now where I've been burned by 3rd party dependencies enough that I basically assume that using anything from npm is like lighting a fuse that'll explode at some undetermined time in the future.
How many active fuses are you willing to light today? How many have you extinguished? How likely is imminent time absorbing doom for your project?
Just opened up the repo for a new project I'm working on called Heximal.
It's goal is to be an HTML-first, declarative system for building dynamic interactive documents, components, and computational notebooks.