is this caching behavior documented anywhere? The only thing I've found is reference to hx-push-url, but not what the default behavior should be.

deleting htmx-history-cache in localStorage clears the problem

tried

still same issue

(and also still seeing htmx-history-cache being added to localStorage)

I'll see if setting cache size to 0 works

yes that looks like the fix

<meta name="htmx-config" content='{"historyCacheSize": 0 }'>

seeing a behaviour with hx-preserve and element: page transitions cause the audio to "jump"

I suspect same issue with video

I think in turbo they used replaceWith? https://github.com/hotwired/turbo/pull/226

also: back button will stop audio completely (in FF at least). The workaround should be to use an Audio object in JS, but if you are initializing this audio in a you need to keep it in a script outside the body

htmx as official spec? Sounds great ... but what do we gain? I think it will just slow down the development. The state of JS in browsers is great these days, so that htmx can get implemented. If there are several implementations by different browsers we just make us unhappy. Instead of one spec, I think more (and different) implementations would help. I hope that soon some smart developer will have a look at htmx and hotwire and then the dev will think "they do it way too complicated, I want it simpler" and he will create something which is even cooler than htmx. And if we would have spec, then what will we do? I think in the current phase diversity is important. I hope to see even more html-fragments-over-the-wire libraries. Ten years later we will know what got used and what not. I don't need a spec, I need an implementation.

Web components have been a thing for a long time, yet have had very little adoption despite the weight of the mighty Google behind them. An official spec is no guarantee of success and @User is right that it would more likely slow development.

Re: more html-over-the-wire: with all the basecamp furore the future of hotwire/turbo looks very uncertain at this point. Probably the only other library I can think of is unpoly, which is undergoing (or about to undergo) a rewrite. Personally I think the idea of html-over-the-wire is sound, but it will depend on solid implementation and adoption (especially by big players so we can answer the manager's question "who uses this in production").

> htmx as official spec? Note that "htmx as spec" doesn't mean copying and pasting the whole htmx documentation into html.spec.whatwg.org right away, rather extending the scope of existing html features in ways that aid hypertext application development (see my post on the wicg topic). htmx and the like would continue existing as a place for new ideas to be tested in the real world. At some time in the future, all these libraries will likely be obsolete for new projects, but when that will happen will be determined by developers, not the spec. > Ten years later we will know what got used and what not. but that doesn't mean we should wait ten years until starting discussions about improving html itself. Spec conversations can go on as htmx/unpoly/hotwire/other development continues and new libraries spring up. These discussions can also give a view of what the general web developer community thinks of html-driven development, which will help htmx.

experimental: shared element transitions with htmx+hyperscript

demo available right now on https://dev.dz4k.com/public/index.pug !

Is there a way to have multiple elements with triggers that target the same target element, and if one has already swapped content into the target, the other does nothing?

Kinda like

once

but for multiple

hx-trigger

elements

I see that I can call a global function as a filter. Maybe I can try that

If that works, is it possible to use non-global functions in there somehow?

I have a growing amount of hyperscript in some of my widgets, and it's time to move this into its own file as a behavior. But I'm running into a problem when I use a tag like this:

<script type="text/hyperscript" src="/static/editor.hs"></script>

. Am I doing something wrong?

you're not doing anything wrong, script src will come in the next release. it's in the dev branch right now

Hey Deniz. Thanks for the help. I thiink I'm using the dev branch right now. I'll double check..

🙂

Since you're still up, is there an example somewhere for the behavior syntax?

yeah, apparently i never opened a PR for it. https://github.com/bigskysoftware/_hyperscript/compare/dev...dz4k:script-src

https://dev.hyperscript.org/features/behavior/ there's one here, but the second one is broken

you can't have variables shared between handlers