This is on mobile, I think you need to tune a bit the menu

Almost certainly because of the enctype attribute on the enclosing form

rollover menus should be built into css or html. Thanks, I'll look into it

the form -

<form action="//127.0.0.1:8001/connect4/group/detail_edit/2" enctype="multipart/form-data" hx-enctype="multipart/form-data" hx-post="/connect4/group/detail_edit/2" hx-target="#detail-target" method="POST"><input name="_formname" type="hidden" value="auth_group"><input name="_formkey" type="hidden" value="eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ0cyI6IjE2MzYyMjc2MTUuMzAzMjY2MyJ9.8mU7kd98i-wnTiZ9HyerXHIRz-il-mRShe0MIWBYCBg">
<table class="table is-bordered is-fullwidth">
        <tbody><tr>
            <td>
                <label for="no_table_role" class="label details-label" title="">
                    Role
                </label>
            </td>
            <td>
                <div class="control"><input class="input" id="auth_group_role" name="role" type="text" value="Administrator"></div>
            </td>
        </tr>
        <tr>
            <td>
                <label for="no_table_description" class="label details-label" title="">
                    Description
                </label>
            </td>
            <td>
                <div class="control"><textarea class="textarea" id="auth_group_description" name="description">tsets</textarea></div>
            </td>
        </tr>
</tbody></table>
    <input class="button is-primary" type="submit" value="Submit"> <span><button class="button is-default" hx-get="/connect4/group/detail/2" label="Cancel">Cancel</button></span>
</form>

i think you need

text/x-www-form-urlencoded

instead of

multipart/form-data

That did it. Looks like my framework is always setting multipart/form-data whether or not there is an upload file. I will test with upload files as well.

Here it is

<div class="container">
      <div class="text-end"><a class="btn btn-secondary" href="/signout">LOGOUT</a></div>
        <h1>DASHBOARD</h1>
        <div class="row">
          <div class="col">

              Search: <input type="text" name="search" hx-get="/search" hx-trigger="keyup changed delay:500ms" hx-target="#results" />

          </div>
          <div class="col">
            <div id="results"></div>
          </div>
        </div>
    </div>

boy thats pretty vanilla, what version are you using?

does

changed

work? I thought it was

change

changed here is a modifier, to test if the input has a new value

1.6.0 from unpkg link

Does the example autocomplete work for you?

Active search I mean

I learned some more today. As you can see in my example, I was using hx-enctype instead of hx-encoding. However, I can set hx-encoding to multipart/form-data for all forms and everything works fine. If I don't set hx-encoding and have my enctype set to multipart/form-data I get the weird results. I assumed that hx-encoding would default to whatever enctype was set to if hx-encoding wasn't set. I'm really confused by the whole thing (obviously).

If you mean the online example then yes. I've not tried to replicate it locally. Update: I swapped out my form with the example and same results. If I return anything from my /search it show those console errors and dies.

week 4 https://thisweek.htmx.org/issue/4/

Hi Everyone. I've just come across HTMX and I am very excited to learn more.

Is this the best place to ask for a little support?

yes!

Thank you! It's related to Django though. Maybe I should ask there?

that's a good idea

Hey folks - I'm scouting HTMX and was wondering if there's a hook to recognize the OS-level dark/light theme choice... I'm looking for a way to retire the janky JS (a redundancy, I know) and have yet to come up with a proper substitute. Any thoughts? Thanks in advance! https://h3tech.dev/post/accessibility/

Are there any relevant hx attributes outside the search area? Or maybe another thing with an

search

id on it?

this would have to be done in hyperscript, it looks like

I'd expect CSS to eventually encapsulate this

Like prefers-dark-theme or whatever the CSS selector is?

I suppose that's my blind spot with HTMX. That funky try-catch-catch is where I'm scratching my head. Perhaps I should ask "in the other direction" - is there a dark mode switch sample in HTMX that's also sensitive to OS preferences?

looks like as long as you ignore IE11, this can be a pure css implementation