https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • if scrolling or something
    c
    if scrolling or something
  • or if not doing any pagination
    c
    or if not doing any pagination
  • the request would be to big
    c
    the request would be to big
  • oh... they said pagination was not an option or something?
    c
    oh... they said pagination was not an option or something?
  • how slow is it to hold it in a js object and then use the client to render?
    c
    how slow is it to hold it in a js object and then use the client to render?
  • or just do paginate
    c
    or just do paginate
  • anyways, in any case I dont see a worker helping for this
    c
    anyways, in any case I dont see a worker helping for this
  • the point of the worker is to just put in another thread expensive computations like fetches and arrays manipulation which could help the ui being more responsive
    n
    the point of the worker is to just put in another thread expensive computations like fetches and arrays manipulation which could help the ui being more responsive
  • you could try that but i dont see it helping. no cpu intensive task, the bottle neck seems rendering a bunch of html. if you paginate appending to the end of an array is extremely cheap
    c
    you could try that but i dont see it helping. no cpu intensive task, the bottle neck seems rendering a bunch of html. if you paginate appending to the end of an array is extremely cheap
  • we may be going off topic
    c
    we may be going off topic
  • for the channel, too
    c
    for the channel, too
  • Good morning all, My HTML5 validation errors are shown when the submit button is placed inside of the form tag but when its placed outside and the form is submitted using javascript like this: `htmx.trigger(form, 'submit-form');` , they do not. I am keeping the button outside mainly because I am dividing the layout into a header, a body and a footer section and the button is in the footer section. Any fixes or workarounds?
    g
    Good morning all, My HTML5 validation errors are shown when the submit button is placed inside of the form tag but when its placed outside and the form is submitted using javascript like this: 
    htmx.trigger(form, 'submit-form');
    , they do not. I am keeping the button outside mainly because I am dividing the layout into a header, a body and a footer section and the button is in the footer section. Any fixes or workarounds?
  • ah ok. yeah then your solution does need js and virtual table and whatnot
    c
    ah ok. yeah then your solution does need js and virtual table and whatnot
  • seems out if scope for htmx
    c
    seems out if scope for htmx
  • Do you guys think HTMX can be used like datatables.js? I feel the Active Search example on the site is doing just that. Am I right?
    g
    Do you guys think HTMX can be used like datatables.js? I feel the Active Search example on the site is doing just that. Am I right?
  • I meant 'using htmx to create functionality similar to datatables.js
    g
    I meant 'using htmx to create functionality similar to datatables.js
  • should be fine
    m
    should be fine
  • https://news.ycombinator.com/item?id=35485826
    m
  • > > Is there anything holding it back from larger adoption? > I don’t know or care. If I were the only one in the world using it, it would make no difference. It’s self-contained and trivial to self host. Big true
    r
    > > Is there anything holding it back from larger adoption? > I don’t know or care. If I were the only one in the world using it, it would make no difference. It’s self-contained and trivial to self host. Big true
  • Can I/should I `defer` htmx and hyperscript?
    r
    Can I/should I 
    defer
    htmx and hyperscript?
  • I know this depends on the use-cases, but I’m wondering if there are any gotchas or issues with that.
    r
    I know this depends on the use-cases, but I’m wondering if there are any gotchas or issues with that.
  • you can use defer for both, but it can introduce ordering issues
    m
    you can use defer for both, but it can introduce ordering issues
  • in general I don't think the small first-time render speed boost is worth it, but it very much depends on your use case
    m
    in general I don't think the small first-time render speed boost is worth it, but it very much depends on your use case
  • Looking at some code, is it odd that `hx-boost="true"` seems to inject the entire response into the `body` tag? I thought that whole point was that it essentially does a `swap` with the new one. Almost like a background `hx-select`. Or am I off on that?
    f
    Looking at some code, is it odd that 
    hx-boost="true"
    seems to inject the entire response into the 
    body
    tag? I thought that whole point was that it essentially does a 
    swap
    with the new one. Almost like a background 
    hx-select
    . Or am I off on that?
  • r

    https://cdn.discordapp.com/attachments/725789747212976259/1094144546599870484/image_3.png▾

  • I am testing something similar right now with go and gomponents and I’m really satisfied
    e
    I am testing something similar right now with go and gomponents and I’m really satisfied
  • It's composable, reusable, and _so fast_.... 🙂 Some folks don't like it, but it really clicks for me.
    l
    It's composable, reusable, and so fast.... 🙂 Some folks don't like it, but it really clicks for me.
  • That particular application had a prior version that was a Vue front-end and a Go back-end. The server working memory set was ~10MB. _chef's kiss_
    l
    That particular application had a prior version that was a Vue front-end and a Go back-end. The server working memory set was ~10MB. chef's kiss
  • On some second thought this seems to be a me issue. Checking out a few other sites using `boost` the server returns the entire template and `htmx` swaps in only the `body` element. Now to figure out why mine inserts the entire template into `<body></body>`
    f
    On some second thought this seems to be a me issue. Checking out a few other sites using 
    boost
    the server returns the entire template and 
    htmx
    swaps in only the 
    body
    element. Now to figure out why mine inserts the entire template into 
    <body></body>
  • Ah ha! `useTemplateFragments` breaks `hx-boost`. Well there we go, now to solve javascript reloading. One step at a time...
    f
    Ah ha! 
    useTemplateFragments
    breaks 
    hx-boost
    . Well there we go, now to solve javascript reloading. One step at a time...
1...108810891090...1146Latest