Trending in Blog Posts
Hey folks,
I just published a post about Hologram’s funding and where the project goes next - the short version:
Curiosum as Main Spons...
New
I am seeing a lot of aplications of Argumentum ad Vericundiam in software discussions. They do link some piece of writing and point us to...
New
Hi all,
In this article, I make the case for each test owning its setup.
Usually I forbid my AI agents to use the setup callbacks; I mu...
New
As I’ve leaned into AI code generation on LocalCents, the volume I ship has climbed, and my worry shifted from any single change to the l...
New
A while back, I had to process millions of database updates in a legacy system that was already hitting its 64 GB RAM limit, so scaling t...
New
I recently figured out how to the the Rust hotpath profiling crate running in an elixir benchmark script (for profiling NIFs). I had some...
New
This article demonstrates how to build a minimal stateful process using only Elixir’s core concurrency primitives: spawn/1, send/2, recei...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










Showing Posts 1 to 6- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
allenwyma
sorry to tag people, but i think this would be interesting to have in LiveView: @josevalim @chrismccord
from my understanding after talking with a CSS DevRel from Google last week, the JS API is more supported than the CSS version for View Transitions. Would this be something that morphdom would need to have or is there an easy way we can “monkey patch” the applyDiff as was done in his example?
The main problem, in my understanding, is that you need to use document.startTransition(async() => applyDiff()), where all of your DOM manipulation needs to happen within the callback.
LostKobrakai
I’ve asked chris about this some time ago on slack. The response was that we doesn’t want to add non-stable APIs into LV, but is open to consider callbacks/hooks, so people can add the necessary integration by themselves.
allenwyma
that’s actually what i’m looking for: if we can have a callback/hook then it would be easy for us to add this in, even if the API changes.
From my understanding, this is “stable” API in the sense that it’s going to be used, and it’s in next version of Safari for both iOS and MacOS, and is already in Chrome.
mssantosdev
I think using view transitions with hooks is doable, but not a good idea.
We would have to add manual UI updates with https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html#push_event/3, which would kill some of the benefits that LV brings to the table.
But I understand the point of not having non-stable APIs into LV core.
LostKobrakai
I’m not talking about the literal js hooks, but another (likely new/to be proposed) callback similar to e.g. the
domcallback you have on the LV constructor, which would allow you to wrap the morphdom change application with the view transition api.mssantosdev
Got it, sorry for misunderstanding you. Yes, having a callback like the one you mentioned is a great idea to handle the API usage.