I have something that may be of interest to you
<body script="on configRequest.htmx put [] into detail.headers">
...
</body>
i want something that takes the place of all the on-* attributes that intercooler had and that makes it easy to catch events and do some stuff directly in HTML, rather than having to drop out to javascript
ic-action too
hyperscript is going to replace all that with a small DSL for event handling and DOM manipulation
i don't know if any of you guys ever programmed in hypertalk, but that was one of my first experiences programming and i had a lot of fun with it
and this will take a huge amount of pressure off me adding features to htmx ;p
@chg20 wow, wondering for days what was wrong with my code on my new sse-body extension. Found out it works in with mock objects, but not real ones :0! So I assume that json-enc doesnt work - or only works with mock objects. When I tried to fix, found out that setHeaders... does not overwrite, but it really appends! WHY!!! ok, lets calm down. So the real fix is to move some code around in htmx, change parameters for encodeParameters -- at least thats what I did to get it to work. Just wondering, is this the way to go??
I think the plugin point is right but the mock xhr is giving bad results
For context, laravel has a global helper to determine whether a request has been made through ajax, which I use to determine if I should return partial html or a full page.
It's easy enough to also check the
X-HX-Requestheader, but I'd like to avoid having to do that on every single request
one sec, let me get an example together for you
would you be willing to contribute a larvel extension to the project when we get it working?
source is here:
htmx.defineExtension('rails-method', {
onEvent: function (name, evt) {
if (name === "configRequest.htmx") {
var methodOverride = evt.detail.headers['X-HTTP-Method-Override'];
if (methodOverride) {
evt.detail.parameters['_method'] = methodOverride;
}
}
}
});
except you don't want to add a parameter, you want to add a header
something like:
htmx.defineExtension('larvel-support', {
onEvent: function (name, evt) {
if (name === "configRequest.htmx") {
evt.detail.headers['X-Requested-With'] = "ajax";
}
}
});
Or whatever the value of the header is supposed to be
you could then use the extension like this:
<body hx-ext="larvel-support>
...
</body>
If that works you can contribute it back as an official extension for HTMX
Specifically, loading data into the subtype dropdown when the primary type dropdown value changes. I've tried setting the trigger to the select2 events, the select element's
change event, few other things, but it's as if the events are never fired.
@36864 just did a video for the value select using HTMX https://www.reddit.com/r/flask/comments/gyplz9/htmx_for_zero_javascript_drop_down_depending_on/?utm_source=share&utm_medium=web2x
hi @chg20 on the script load there is pretty expensive traversal of full DOM which results in decreased Lighthouse scoring because of the longer main thread work, is it possible to separate this logic for projects not using extends and other features that might require initialization? standard listeners might work well when bound to document root so it wouldn't be necessary to find and bind them in the DOM
I don't want to change the init code @oko-x but I will :/