llcooliovice

5 ms·

1.
Chrome Prototypes HTML Includes(github.com)
1 points by llcooliovice 2mo ago|1 comments
2.
by llcooliovice 2mo ago
Chrome are prototyping a declarative client-side include mechanism. <template src="/partial.html" for=""></template> Together with the declarative API, it will also include a way to import HTML in J
3.
Implementing dark mode with standard CSS(olliewilliams.xyz)
3 points by llcooliovice 3mo ago|0 comments
4.
Ongoing attempt to standardise a DOM Templating API in browsers(github.com)
1 points by llcooliovice 3mo ago|0 comments
5.
Trusted Types and the Sanitizer API(olliewilliams.xyz)
1 points by llcooliovice 11mo ago|0 comments
6.
Declarative Partial Updates Proposal(github.com)
2 points by llcooliovice 1y ago|1 comments
7.
by llcooliovice 1y ago
HTML primitives for updating parts of a document without a full page refresh
8.
Front end complexity and the HTML Renaissance(olliewilliams.xyz)
2 points by llcooliovice 1y ago|0 comments
9.
by llcooliovice 1y ago
Interop is such a good idea, I’m surprised more developers don’t participate.
10.
Declarative Route Matching Proposal(github.com)
3 points by llcooliovice 1y ago|0 comments
11.
Ripple: new JavaScript framework from an ex-React & Svelte core team member(github.com)
13 points by llcooliovice 1y ago|7 comments
12.
by llcooliovice 1y ago
From Dominic Gannaway, the creator of Inferno, who worked on React at Meta and on Svelte 5 at Vercel. Feels like a hybrid of React and Svelte 3/4.
13.
by llcooliovice 1y ago
> We've explored the reactivity landscape. While early DOM templating proposals didn't include updating, userland systems have thoroughly explored the landscape by now, and discovered good mental models and better and worse imp
14.
by llcooliovice 1y ago
> If the Records and Tuples proposal were progressing, JSX could maybe create Records with boxes, but that proposal has been stalled, especially on the record identity and box parts that would make it suitable for a JSX semantics. That
15.
by llcooliovice 1y ago
> There are in-flight proposals for very low-level DOM update primitives, like DOM Parts, which target framework implementations, but I think higher-level APIs like full declarative templating can take even more load off, help prove out
16.
by llcooliovice 1y ago
Chrome implemented a prototype, then the spec changed and they removed it, then they implemented the new version. I should have been clearer and said Chrome Canary and Firefox Nightly. Not sure when it will reach stable but probably some po
17.
by llcooliovice 1y ago
> There's no fundamental templating knowledge that's portable between stacks, and native DOM creation APIs like innerHTML are unsafe by default. setHTML() is already implemented in Chrome/Edge and Firefox so this point is
18.
by llcooliovice 1y ago
There is still innovation happening in frameworks. I do wonder if it is too early to start adding things like this to the browser. Web components landed way too early and now we’re stuck with them.
19.
by llcooliovice 2y ago
A better non-modal dialog using the popover API.
20.
A Modern API for Cookies(fullystacked.net)
1 points by llcooliovice 2y ago|0 comments
21.
AV1 video codec gains broader hardware support(fullystacked.net)
323 points by llcooliovice 3y ago|202 comments
22.
by llcooliovice 3y ago
Now supported by the Apple M3 chips.
23.
The View Transitions API, the Navigation API and the SPA vs. MPA Debate(fullystacked.net)
2 points by llcooliovice 3y ago|0 comments
24.
Tables no longer needed for HTML email(fullystacked.net)
170 points by llcooliovice 3y ago|115 comments
25.
by llcooliovice 3y ago
With the modernisation of Microsoft Outlook, if will finally be possible to code an email in a semi-modern way.