@User for you: https://github.com/bigskysoftware/htmx/commit/1d52b23fed26c48f19e2dd352c3d325905acbeb3

Eventually we will default that to true and you'll need to opt in for IE11 support

once the guinea pigs, er, early adopters work any, er, issues out

Or even a

htmx.legacyBrowsers

flag that's used in several places.

revealed

would be another candidate.

side note: I dropped the settle time from 100ms to 20ms. Turns out humans notice at around 100ms (which is why I picked that) but browsers setTimeout(..., 100) actually usually takes longer than 100ms

This is what I call “The patience of Job” 😂

Not a bad idea. Maybe here? https://htmx.org/docs/#3rd-party

probably better to have its own place on the docs and not shared with the 3rd party, which is something else. Just my 2c

@User Following our conversation about supporting something like hx-function/hx-action in htmx, I created a pr with a rough implementation to show how it could work, including some examples you can try out in the scratch.html. What do you think? https://github.com/bigskysoftware/htmx/pull/493

Hi tony, I like it. Would you mind implementing it as an extension first so we can experiment with it for a bit? I wonder if it would make sense to have both a

hx-js-action

and

hx-hs-action

for javascript and hyperscript

Yeah sure. I will look into implementing this as an extension. But about having

hx-js-action

and

hx-hs-action

, wouldn't that make htmx integrate too deeply with hyperscript? I think I like the idea of htmx being actually like an extension to html, and it would be nice to have an

hx-action

that feels a lot like onClick or onChange html attributes. But i see your point. Especially for hyperscript, the ergonomics of calling hyperscript inline via an interop funcion is not great. How about having hx-action that defaults to js, and then hx-hs-action that works with hyperscript? Or having 2 attributes;

hx-action

, and

hx-script

.

hx-action

would be either js or hs, or any future script, and then

hx-script

would be either

js

or

hs

or any future script, and when not set, defaults to javascript? There's also the option of only defining the hyperscript actions in a script tag, and only calling the hyperscript functins via the interop. eg

html
<script type="text/hyperscript">
function doStuff()
  put "abc" into #btnID.innerHTML then
  toggle .hidden on #modal
end
</script>
<button hx-trigger="click[metaKey]" hx-action="_hyperscript.evaluate(doStuff())">close</button>

The interop can also be aliased to something like

action="_hs.e(doStuff())"

I'm not sure which option is best. Though I would lean more towards

hx-action

, and

hx-script

or just supporting only javascript and interop. Sorry for the lengthy write up.

no worries: your extension your decision 🙂 Let's see how it turns out

By the way, could you give me a hint about how this could be implemented as an extension? It doesn't seem like there's a way to create new attributes via the extension api

js
{
    onEvent : function(name, evt) {return true;},
    transformResponse : function(text, xhr, elt) {return text;},
    isInlineSwap : function(swapStyle) {return false;},
    handleSwap : function(swapStyle, target, fragment, settleInfo) {return false;},
    encodeParameters : function(xhr, parameters, elt) {return null;}
}

you would want to handle the

htmx:load

event and wire in your stuff there, one sec

looks like the

htmx:afterProcessNode

event might be the right thing

that's a good template for what you want

usage: https://htmx.org/extensions/class-tools/

Awesome! Thanks

@User FYI, sending your https://github.com/rajasegar/awesome-htmx along to someone interested in learning about more practical HTMX

thank you!

I have finished up most of the 1.4 dev for htmx. If you have any issues you want to make an argument for, do so in the next day or so.

sometimes i really love intercooler/htmx

Running into issue with htmx that's driving me nuts: I have hx-boost with target as content div. Works fine, except in mobile browsers: when re-opening the page it will open with the instead of full page reload.

i.e. if the browser is closed & re-opened

I've set meta {"historyCacheSize": 0}, Cache-Control "no-cache"

makes no difference

"htmx will need the entire page when restoring history if the page is not in the history cache." so that implies that if cache size is zero, it should reload entire page