https://htmx.org logo
Powered by
# htmx-general
  • g
    i would recommend against using mousedown. often i mousedown on things but then decide not to open them. If you want to speed up loading, a better option is to use the preload extension
  • s
    i hink mousedown trigger on navigation/menu elements are a fairly common theme in most ui's .. see almsot all windows programs.. while mouse release triggers for buttons and other more deliberate actions.
  • a
    Check out the preload extension as Deniz said, it's based on another open source lib and already caters for several edge cases (I think mobile touch events too, if I recall correctly), plus it's configurable ito how aggressive you want the preloading to be, e.g. you can preload on mouseover as well, if the mouse stays on the target for more than x millis, etc. I had issues with it not really working before, due to our reverse proxy/WAF injecting different headers into requests than when you mouseover only and the preload extension makes the request, but it may work for you
  • a
    To see it in action, check out the htmx website, the top nav links are loaded using it 🙂
  • p
    I am testing out this thing and I am still unsure how to structure the code correctly? Do you save these snippets in separate html files, or do you just live the inlining and no help from your editor?
  • h
    I mean I would prefer it to live in a template file
  • h
    and use jinja
  • h
    but keeping templates in components is standard practice in a lot of the world (jsx, lit)
  • m
    i have no idea how to organize this thing, what do you suggest?
  • l
    probably in making categories in server settings
  • l
    like General (general, showcase), Python (django-htmx)
  • m
    @User you decide and lmk
  • b
    Vote for General [welcome (default, no user chat, just some love from 1cg and/or Deniz about the mission, links), showcase, hyperscript, htmx-help], then Stacks [ python, go, django, etc ]
  • b
    I chose Stack because it's not quite Languages (django, hotwire), but I couldn't think of a better word
  • l
    or more like 
    announcements
    (that closed one) for new versions etc
  • m
    @User rate my boomer-tier organization
  • h
  • r
    This is much better, thank you
  • h
    302's from a boosted link do not change the url - is that expected? I would have expected the 302 to be caught by the browser and never touch htmx
  • m
    the final URL isn't being pushed?
  • m
  • h
    I can poke at it tomorrow
  • h
    this is my playwright test that's failing:
  • h
    Copy code
    def test_login(self):
        page = self.context.new_page()
        page.goto(f"{self.live_server_url}{self.url}")
        page.wait_for_selector("text=Log in/Sign up")
        page.fill("[name=email]", self.user.email)
        page.click("button")
        page.wait_for_selector(f"text=Welcome back, {self.user.first_name}!")
        page.fill("[name=password]", self.password)
        page.click("button")
        actual = page.url.removeprefix(self.live_server_url)
        self.assertEqual(actual, "/")
  • h
    a normal click works
  • m
    w/ ajax do you need a wait in there?
  • m
    does playwright sync on full page requests?
  • h
    I think I need the wait, the server needs a chance to swap the content in
  • h
    idk
  • h
    I think what I'm going to do is instead of a 302 do hx-redirect
1...566567568...1146Latest