Though Hotwire is mentioned namely, I guess it's interesting that the approach is mentioned in the report.

Is there a way to get the code that handles the debug info in the bottom of the documentation examples?

the count of server requests + outgoing data and response

it would be very useful to drop into an app as a debug tool

that's built into the mock server that HTMX uses, however a similar thing could be built for real server requests

HTMX on the explore page

lol wut

Hello everyone, I'm trying to get "hx-ws" flow working in combination with "hx-trigger" is it possible to start the Websocket connection after some other trigger ? The underlining idea is to create a cookie & pass that information to a websocket. I tried the following:

Piece about Roy Fielding on Hacker News: https://news.ycombinator.com/item?id=29009729

the battle is joined!

The official name of this project/technology - is it "HTMX" or "htmx"? (Pedantic bloggers want to know!)

htmx, lowercase

our non-existent styleguide at This Week in HTMX mandates lowercase (despite the name of the site itself)

Cool - I... uh, I mean... pedantic bloggers wanted to make sure they got it right. 🙂

also, hyperscript is _hyperscript, and the underscore is silent

under no circumstances should hyperscript be spelled hyperscript

_hyperscript, worsening your markdown experience since [however long it's existed]

ah yes, my favorite programming language \\_hyperscript

🤣

Hi guys, I'm working on a browser extension that uses htmx for the popup, and certain responses send a

hx-trigger

header to fire off javascript functionality like communicating with background and content scripts, etc. I am having a very frustrating problem where for some reason, the hx-trigger header is not triggering client side events. I traced it back to the fact that as soon as the ajax request comes back in the

xhr.onready

handler defined inside of

issueAjaxRequest

, the headers are incomplete. This is the output of

responseInfo.xhr.getAllResponseHeaders()

on the first line of the onready function:

content-length: 220
content-type: text/html; charset=utf-8

However, these are all the headers on the response:

HTTP/1.1 200 OK
Date: Wed, 27 Oct 2021 20:27:06 GMT
Server: WSGIServer/0.2 CPython/3.9.6
Content-Type: text/html; charset=utf-8
Hx-Trigger: setupLogin
X-Frame-Options: DENY
Content-Length: 220
Vary: Cookie, Origin
X-Content-Type-Options: nosniff
Referrer-Policy: same-origin
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin: chrome-extension://kcegdmcjklppcfbmfjgkkomecpaofoec

Any advice? I am really perplexed

I also posted this question on stack overflow: https://stackoverflow.com/questions/69743602/xhr-getallheaders-is-missing-some-headers-in-a-browser-extension-context

yeesh

I have no idea

💀

My thought would be that maybe Chrome isn't giving extensions all the headers on purpose, for some security-related reason? Maybe you have to opt into headers?

yeah, I am thinking something in that direction too

I already have this handled: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Headers

so it's not that

But I mean that is for request headers not response headers, so doubtful that it's relevant