htmx

only diff between 0.1.0 and 0.1.1 should be not doing the double dispatch when kebab and camel names match

I am looking at the diff now, trying to understand what's going on

So If I download 0.1.0 and manually change what you fixed for 0.1.1, then it works. But if I use 0.1.1 directly, it doesn't work. Tried it in a private browser window, and it's the same. No idea what's going on

<@725789255590215732> The issue seems to be coming from the changes here. This is a difference between 0.1.0 and 0.1.1 downloaded from https://unpkg.com/

Is there a way to pass query string parameters to requests triggered by htmx? E.g., if I'm on page http://example.com/?x=1 and it contains `<div hx-get="/foo" hx-trigger="load"></div>` I would like to pass `x` in `GET /foo` request

<@!251810469822726145>  You can use `hx-vars="x:1"`

how would I get that `1` from URL into hx-vars?

Ah, you can also use a computed function in hx-vars

<@!725789255590215732> So this seems to fix it in Chrome, FF and Safari:

```js
//AK - FIXED CHROME issue - "refuse to get unsafe header" warning.                       
if (xhr.getAllResponseHeaders().indexOf("HX-Trigger".toLowerCase()) >= 0) {
    handleTrigger(elt, this.getResponseHeader("HX-Trigger"));
}                      

if (xhr.getAllResponseHeaders().indexOf("HX-Push".toLowerCase()) >= 0) {
    var pushedUrl = this.getResponseHeader("HX-Push");
}
//AK - FIXED CHROME issue - "refuse to get unsafe header" warning. \\
```

<@!564583361117421644> - earlier this morning you were asking about mocking a back end from within Javascript.  HTMX's test cases already do this, using a librarycalled Mocha.  If you're looking to make a platform-agnostic TODO demo, check out some of the manual test cases for an example.

Lost threads like this are why IM/Slack/Discord suck so much.

<@!732737380167188501> <@!564583361117421644> You may also want to have a look at mirage.js

ugh, I think I merged that change into master and not dev, so it showed up in 0.1.1

thanks for the catch, too bad we can't really test case sensitivity

<@!578303204392173604> i just put out 0.1.2

should fix your issue, and I added a case-sensitivity test

<@!578303204392173604> - thanks for the tip.  I hadn't heard of either one of those until recently 🙂

For what it's worth "DOM processing should be fast" always fails on my older i7 desktop, it takes 156ms.  I like the other tests that show the time in ms in red.  Most of the timing tests are in red.