|
From: | Jim Porter |
Subject: | bug#69232: 30.0.50; [PATCH] EWW history navigation gets caught in a loop |
Date: | Mon, 19 Feb 2024 10:55:49 -0800 |
On 2/19/2024 4:12 AM, Eli Zaretskii wrote:
I'm not sure this is a bug fix, and I think this behavior change does need a NEWS entry.
Ok, I added one.
And have sure you are that no one will want the current behavior?
Well, I suppose I can't prove that there's no one who likes the current behavior. I'd be pretty surprised though, since I've never seen a browser that manages back/forward navigation like this.
In *theory*, a person might be able to (ab)use this to track changes to a given page across refreshes, but that doesn't work consistently, since EWW doesn't always add a new history entry upon reloading. Given that you have to jump through some hoops to trigger this behavior (for example, this doesn't work if you're at a new page not in 'eww-history' yet), I doubt anyone has noticed that this is possible. On the off chance that someone wants a feature like that, I think we could do it in a better way, anyway.
If you're still concerned that someone might prefer the current behavior, I could announce the change to emacs-devel after (or before) it merges in order to give people an opportunity to speak up.
0001-When-navigating-through-history-in-EWW-don-t-keep-ad.patch
Description: Text document
[Prev in Thread] | Current Thread | [Next in Thread] |