https://htmx.org logo
Powered by
# htmx-general
  • h
    let me update to remove the revealed in data state since that's doing nothing
  • m
    roger
  • h
    k updated
  • h
    I have another stupid question that I can't figure out if it's a bug or not. In that table of item I'm lazy loding, the 20th item holds the hx-trigger and hx-get target. If you click the a tag on that row while hx-boosted is true, rather than fire the a tag's normal behavior of following the link it's triggering the hx-get's behavior
  • h
    If boosted is not true then the link's href is followed like normal
  • h
    If I try to do hx-get="unset" on the a tag then it tries to grab the literal page "unset"
  • m
    🤦‍♂️
  • m
    can you post as simplified as possible an example?
  • h
    if you got to https://animelister.fly.dev/ and click on the 20th item it'll do it
  • h
    notice it will change the url correctly but scrolls to the top of the table
  • h
    you want me to make a stripped down example for a test case?
  • m
    that would be ideal
  • m
    at the very least we can explain the behavior
  • h
    awesome, will do
  • m
    one thing I notice when viewing the source is the hrefs don't appear to have quotes:
  • m
    not sure if that makes a difference
  • h
    nope, sadly 😦
  • h
    the version of node-sass used for running the tests is super old
  • h
    I got it working with node 10 but it barfed on 16
  • h
    I am weak with js testing - where does the 
    make
    function come from that's used to create the html snippets?     I swear, asking the question leads to the answer half the time
  • h
  • h
    it's the hx-swap="afterend" that's causing the bug
  • h
    the test fails on the second case and passes on the first, and the only difference is the afterend
  • g
  • h
    yeah and adding 
    hx-swap="unset"
    to my inner link fixes the bug
  • h
    Is this a bug? I guess the a tag is inheriting the hx-swap "correctly" but in this case it'll never be the intended behavior for the swap to move down
  • e
    Quick question: if I want to set the config variable 
    allowEval
    to 
    false
    , don't I just need to add 
    <meta name="htmx-config" content='{"allowEval":"false"}'>
    to my page head? Asking because... it's not working and I need this because my site enforces strict CSP. Or looking at the source code https://github.com/bigskysoftware/htmx/blob/e9434be4430864e78401fb982edfe39392a022f6/www/test/1.6.0/src/htmx.js#L2109 can I conclude that if I want to have strict CSP (and thus no 
    eval
    ), I have to kiss goodbye to custom JavaScript in event filters?
  • m
    Ah, OK. So this is a case where inheritance isn't doing what we want, but it's expected behavior. 😑
  • m
    that's correct, you have to give up event filters if you disallow eval
  • m
    we should make it pluggable so you can write an event handler if you want
1...417418419...1146Latest