3 ms·
i think the transition API, when it is broadly available for MPAs, could replace a fair number of simple UI use cases of htmx. The main feature it would likely
by recursivedoubts 2y ago
i think the transition API, when it is broadly available for MPAs, could replace a fair number of simple UI use cases of htmx. The main feature it would likely obsolete is the `hx-boost` feature:
https://htmx.org/attributes/hx-boost/ https://htmx.org/attributes/hx-boost/
There are already people, including people on the core htmx team, who think that hx-boost isn't a great feature:
https://htmx.org/quirks/#some-people-don-t-like-hx-boost https://htmx.org/quirks/#some-people-don-t-like-hx-boost
If that goes away, htmx will be useful for smaller transclusional features at a lower level of complexity, so the two should complement one another in my opinion.
- seanwilson 2y ago> If that goes away, htmx will be useful for smaller transclusional features at a lower level of complexity Thanks! Any examples here to help understand where View Transition doesn't help?
- recursivedoubts 2y agoI think active search (submitting requests as you type) is an example of something that View Transitions don't help with: https://htmx.org/examples/active-search https://htmx.org/examples/active-search