Post

@_developit I've been doing this for years!
whistlr.info/2020/control-l…
English

@_developit @mathias I'm a little worried about the accessibility announcement this will generate... Maybe it's fine if you're largely using it for full-page effects that deserve a "loading" announcement anyway?
English

@_developit More about this here: #intercepting" target="_blank" rel="nofollow noopener">developer.chrome.com/docs/web-platf…
English

@_developit Please only do this with sufficient delay (300ms or so) to allow for most round-trips on a good connection to resolve before showing the spinner on every click!
Otherwise your page will feel slower and somehow broken.
English

@_developit @noseratio Is there a chance you could click the 'stop loading' button a fraction too late and inadvertently refresh the page?
English

@_developit I can't avoid hating this idea - the spinner and everything outside the page belongs to the browser user and needs to reflect the browser's state. These UI elements need to be trusted by the user and making them accessible this way to code on the page breaks that trust.
English

@_developit Wow, it's disgusting. Now user even can't be sure the cause of appearing of this spinner.
Because it may be because resources still loading (default behavior) or maybe some developer enable it just for fun or due to bug
English

@_developit Waiting for an API to simulate the page reload, without actually reloading the page
English

@_developit But which effect would stopping it have since promises are not cancellable?
English

@_developit @htmx_org Easily using this in a way with htmx-indicator would be amazing.
English

@_developit I was playing with that + the client transition API recently: #L6" target="_blank" rel="nofollow noopener">github.com/jacob-ebey/htm…
English

@_developit This is great, but only if pressing the "Stop" button actually does something. Many AJAX libraries don't support that even via ESC
English










