https://htmx.org logo
Powered by
# htmx-general
  • p
    If I understand correctly, if you had hx-boost on the body of your page (or container div or whatever), does it supercede all hx-get/hx-post events? So if I have an with hx-get, the hx-get event is ignored?
  • m
    no, the hx-get should override it
  • p
    Yep, just tested, that works fine
  • p
    I was thinking: suppose I wanted to write an hx-trigger for IntersectionObserver as a plugin - say hx-trigger="intersect". Is there an easy way to add new plugins for that kind of behavior?
  • m
    Absolutely, in fact that would be a great plugin idea!
  • m
    The remove-me extension might be a good basis:
  • m
  • m
    Here's something to get started https://codepen.io/jreviews/pen/wvgLZoZ
  • p
    yes, I've got something similar so far (though good tip re using "enter"). Issue is just getting the htmx import to work
  • p
    import htmx from 'htmx.org';
  • p
    htmx.defineExtension not defined...
  • p
    defineExtension should be public API
  • p
    ok icky af but works
  • p
    window.htmx.defineExtension('intersect', {
  • p
    and working
  • p
    pretty much as per codepen from @User
  • p
    I think I ran into this issue around modern imports: https://github.com/bigskysoftware/htmx/issues/34
  • p
    is there a specific event to watch after an hx-boost resolution? Looks like the same scrolling issue when you have height: 100% or similar in the css is preventing scroll to top, so need to override that behavior
  • p
    also interesting:
  • p
    htmx.defineExtension('intersect', { onEvent(name, event) { console.log('intersect!', name);
  • p
    so the extension onEvent does not fire on immediate page load. Only after some interaction (e.g. after link through hx-boost)
  • p
    i.e. no event gets fired at all
  • p
    I suspect this is an npm issue
  • p
    sorry fixed: I had "defer"
  • s
    htmx.org is cleaner than 91% of websites https://www.websitecarbon.com/website/htmx-org/
  • p
    I'm hitting this issue https://github.com/bigskysoftware/htmx/issues/123 (legacy form relying on behavior of button values). I tried workaround with hx-vals on each button, but this doesn't appear to work - values of hx-vals are not passed
  • p
    in the docs it states "A child declaration of a variable overrides a parent declaration."
  • p
  • m
    OK, sorry about that. I am taking this week off but will attack issues early next week.
  • p
    Is there a better workaround than hx-vals perhaps?
1...235236237...1146Latest