Is it possible to simulate with htmx?

yes

here's the code:

html
<a href="...">

What do you mean by that?

for example i want to have button, which after click, will redirect me to the other site

why does it have to be a button?

because i dont want to create a css class which will be the same as the button class 😛

if it's for aesthetic reasons, it's much preferable to use css

okay

i get it

damn you css

i wish css had more options to make it more reusable

I was getting ready to say you could use css to make the

a

element look like a button.

i think i have a class somewhere that normalizes buttons and links to look the same so you can add styling on top of that

i know i can do this that way

i was just curious

You could also use

hx-get

and return an

HX-Redirect

header, or you could just wrap the button in a get form

No need to get too fancy with it

wrapping button with form sounds like an idea

Just pretend it's 1999 again

xD

Thanks for looking over the changes and for your additions. A few thoughts: 1. The reason that I thought

ajaxHelper

was public is because of the comment here (https://github.com/croxton/htmx/blob/03c3e871313dcc73132d8a69de07ab6cbbe021be/src/htmx.js#L16). If indeed this function is public, then the variable

path

that we are using as the

hxLocationHeaderPath

will not always be tied to

Hx-Location

. Some extension using this function would probably break. This leads me to advocate for either changing the parameters that

ajaxHelper

takes OR, preferably, to not use that function when handling the

Hx-Location

header. @mysterious-toddler-20573 should this function be treated as public? 2. In terms of the main change from my code to yours where you pass the swap spec source element (https://github.com/croxton/htmx/blob/refactor/hx-location/src/htmx.js#L3058), I think the reason to do this is as you mentioned to "act like following a hx-boost link" by respecting other attributes on the element. While I believe you are correct that this would bring

Hx-Location

in line with the documentation, this is a bigger change that means making

Hx-Location

play nice with all the other attributes on the element. It is a good sign that existing tests pass, and I wonder, do we need any new tests? If new tests are required, could we make a PR with my changes and then a future PR with your change + new tests? 3. @hundreds-camera-24900 @mysterious-toddler-20573 In general, I wonder if the scope of

Hx-Location

is too big. Does it really need to have a callback that could be passed in via a header? I really appreciate you all looking into this - I love HTMX+Alpine as an alternative to Vue/React, and supporting use cases for the

hx-history-preserve

extension is vital to be able to ditch those frameworks.

yup, css option is the best

thank you for this awesome example

🙂 thank you, definitely feels like I'm not doing a great job

@limited-potato-46306 1. I see, looks you are right. 2. It currently supports a source element if passed via the json in the header though, so attributes should already be supported. There isn’t a test for that though. Probably should be a separate PR as you say.

ajaxHelper

is exposed at just

htmx.ajax

@hundreds-camera-24900 do you have any thoughts on

HX-Location

here? I have to admit I'm not really up to speed yet.