htmx

Do you happen to have `scroll-behavior: smooth` in your site's CSS?

There is the `htmx.config.scrollBehavior` setting that you can change to `auto`

Unfortunately this doesn't seem to be it (no such css), but thanks for the tip

<@725789255590215732> Thanks that worked!

<@485066180537614346> FYI your site htmldriven.dev appears offline again. :(
(The reason why I keep tabs on it is because I'm giving a talk at this year's CraftCMS DotAll conference about "HTML over the wire", and your site is an invaluable resource!)

So most of the time in the past I've had a button to trigger forms, and an a tag styled to look like a button

that's part of the general look and feel of a site

I'd like to just use one from now on - either hx-get on a button or hx-post on the link

and I"m trying to decide which is better from a ux pov

Right now I think using a link everywhere is better since that will allow middle click to work when it's a normal link styled to look like a button

are there any downsides for a form submission? I can't see one

I don't have to grapple with "is this a button-button or a button-link"

you know how in http semantics, GET has no side effects?

you could have one component that changes its tag, no?

that wouldn't be terrible but I don't see why

using a link like a button would be like `<a hx-post="closest form">`

HTML: making it impossible to do things right easily since <div>

afik that doesn't run the risk of the borwser doing something stupid like preloading the submit, since there's no href to preload

Depending on what type of form it is CSRF-mitigation can be a good point to keep using POST