feat: Add option to disable previous URL storage

[neznaika0]

Closes #81
Copied isWeb() - it private method
The test may be inaccurate, correct it

[michalsn]

I have second thoughts on this topic. When working with htmx, we may often want the page loaded by the htmx request to be stored as the previous URL.

My point is that in some cases this can be helpful, but for others, it will be a problem... so IMO we should make this option configurable.

Maybe $storePreviousURL option in the config file, with the default value set to true to preserve BC?

[neznaika0]

An example of specific cases? Yes, the setup is not a problem
What about the AJAX option? It does not save by default. If the HTMX is configured with AJAX headers, the option has no effect.

[michalsn]

An example of specific cases?

An example would be using htmx in the navigation to simply navigate to another page. In that case, we won't be storing the previous URL in the session at all.

When AJAX headers are used, it is the user's choice. We will not override the default behavior of the framework.

[neznaika0]

No 😄 . An example where the previous URL is needed.
In the userform > formhandler > userform chain, sometimes the previous URL may be formhandler.
I want to avoid this.

Plus, there are questions about the framework when working with browser tabs... there, too, the URL is overwritten.

I'll update the PR tomorrow. I would be grateful if we discuss it in more detail.

[michalsn]

It is not important where it will be used, only whether it will return correct data. If you disable updating the previous URL for htmx requests, then it may have an incorrect value.

Plus, there are questions about the framework when working with browser tabs... there, too, the URL is overwritten.

Yes, the same way as for traditional requests - we won't change that.

[neznaika0]

You have almost completely corrected the PR. Fix it faster for you

[michalsn]

You did 90% of the work here. Thank you.

[neznaika0]

@michalsn I caught BC 😄
Let's say there is a "Show deleted" checkbox in the list of users. After clicking, HTMX changes the URI in the browser, but not in the history. If we click another button/link and try to return to the current URI (as previous_url()), it will turn out to be the old one (before clicking the "Show deleted" button)
Now I fully understand your pagination example.

So I haven't completely solved my problem.

[michalsn]

What is your problem? Sometimes you want to store the previousURL even if it's disabled?
Or are you referring to the browser history?

[neznaika0]

The example with pagination is simpler:

1. Go to /users
2. Click to pages Next/Back from HTMX and stop at /users?page=10
3. Click on the button with HTMX /users/ban/33 and return to the same page (via previous_url()) Ops.. We should go back to /users?page=10 but the story is disabled - we get to /users

Now I have forgotten the exact example of the initial problem. But apparently this is not how it was planned.

EDIT: A good solution is to use HX-Current-Url as it sends the URL of the start page. It is similar to the Referer but looks more reliable

[michalsn]

Why not use ajax-header extension for places where you want don't want to store the URL?

[neznaika0]

Let's leave this question for now. When I find the exact example, I'll come back.