This addresses problems using the WebSocket extension to send messages to a websocket server. We were calling `shouldCancel` with the incorrect API signature, causing it to return FALSE (as in, don't cancel the event) when it should have returned TRUE (as in, yes, cancel the event)
I don't know why this worked in my tests before, but the test case it behaving correctly now.
The stylesheet was preventing the "echo" test from working correctly. WS messages were sent/received correctly, but the results could not be displayed because the container size was too small. This patch allows the containers to grow, and display WS results correctly.
As per #800.
* Recommend downloading htmx as the main way of installing it.
* Cover npm installation in a bit more detail.
* Note the downsides of unpkg.com and always recommend with the integrity SHA.
* Use `<script defer>` in all `<script>` examples. This tells the browser to defer the parsing and processing of the script until all content is on display, increasing performance. [See HTML spec diagram](https://html.spec.whatwg.org/multipage/scripting.html#attr-script-defer).
* Add data-loading-aria-busy directive for loading-states extension; add tests for the extension
* Update docs
* Fix tests of scoped loading states
* Commit test files
* Improve delay tests by using sinon timer
* Add reference to MDN about `aria-busy` attribute
Scheme-relative URL’s were invented when HTTPS was slow, so HTTP pages could load resources insecurely, but a little faster. There’s no need to use them now as HTTPS is fast, and everything should be secure.
* load htmx and hyperscript after mock-request, so you can use `init` and `load` correctly
* disable all disableable elements while the demo environment is loading
* support a `delay` attribute on templates to specify a delay
* merged @dz4k's excellent simplification to the eval code
