11cef8ee83
* Process sse-swap properly when swapped in Previously `sse-swap` were only processed when `sse-connect` was on the root of what was being swapped in. This is now fixed so that the closest sseEventSource is found and used as the event source * Pass for code readabiltiy remove the nested if statements as there is no difference in handling between sseURL and LegacySSEUrl. * Fix indenting * Initial attempt at sse extension tests * Make existing tests pass * Add test case for #916 * backport test for #916 to hx-sse for completeness * add a distinct test for sse-swap * more tests, fix tests + more tests differentiating the implementation of sse-swap and hx-trigger * fix for "is closed after removal with no close and activity" * Cleanup listener if element is gone * Revert "Cleanup listener if element is gone" This reverts commit bbe3715276302656d1a422fbc4778842776e35f6. * Clean up listeners if element gone, fix indenting * Incorportate feedback from first review + seperate eventSource creation logic and event registering logic + manually create event handling, still confused by how hx-trigger works * `createEventSourceOnElement` now looks for event sources in children * explicitly handle legacy sse handling instead of having extra selectors in `querySelectorOnThisOrChildren` + a few readability changes + add regression check to make sure that sseEventSource is only created on elements with sse-connect or equivalent + add test to make sure that sse-connect in the child of a swapped element is handled * Allow multiple listeners in eventsource mock * Backport eventsource mocks to legacy tests --------- Co-authored-by: 1cg <469183+1cg@users.noreply.github.com>
high power tools for HTML
introduction
htmx allows you to access AJAX, CSS Transitions, WebSockets and Server Sent Events directly in HTML, using attributes, so you can build modern user interfaces with the simplicity and power of hypertext
htmx is small (~14k min.gz'd), dependency-free, extendable & IE11 compatible
motivation
- Why should only
<a>and<form>be able to make HTTP requests? - Why should only
click&submitevents trigger them? - Why should only GET & POST be available?
- Why should you only be able to replace the entire screen?
By removing these arbitrary constraints htmx completes HTML as a hypertext
quick start
<script src="https://unpkg.com/htmx.org@1.9.10"></script>
<!-- have a button POST a click via AJAX -->
<button hx-post="/clicked" hx-swap="outerHTML">
Click Me
</button>
The hx-post and hx-swap attributes tell htmx:
"When a user clicks on this button, issue an AJAX request to /clicked, and replace the entire button with the response"
htmx is the successor to intercooler.js
installing as a node package
To install using npm:
npm install htmx.org --save
Note there is an old broken package called htmx. This is htmx.org.
website & docs
contributing
Want to contribute? Check out our contribution guidelines
No time? Then become a sponsor
hacking guide
To develop htmx locally, you will need to install the development dependencies.
Requires Node 15.
Run:
npm install
Then, run a web server in the root.
This is easiest with:
npx serve
You can then run the test suite by navigating to:
At this point you can modify /src/htmx.js to add features, and then add tests in the appropriate area under /test.
/test/index.html- the root test page from which all other tests are included/test/attributes- attribute specific tests/test/core- core functionality tests/test/core/regressions.js- regression tests/test/ext- extension tests/test/manual- manual tests that cannot be automated
htmx uses the mocha testing framework, the chai assertion framework and sinon to mock out AJAX requests. They are all OK.
You can also run live tests and demo of the WebSockets and Server-Side Events extensions with npm run ws-tests
haiku
javascript fatigue:
longing for a hypertext
already in hand