From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, James Thomas <jimjoe@gmx.net>
Cc: 69232@debbugs.gnu.org
Subject: bug#69232: 30.0.50; [PATCH] EWW history navigation gets caught in a loop
Date: Sat, 24 Feb 2024 14:29:21 -0800 [thread overview]
Message-ID: <b643f144-1cea-4685-d4c1-624580bb708c@gmail.com> (raw)
In-Reply-To: <8634tiymd4.fsf@gnu.org>
On 2/24/2024 6:20 AM, Eli Zaretskii wrote:
>> Cc: 69232@debbugs.gnu.org
>> Date: Sat, 24 Feb 2024 19:45:49 +0530
>> From: James Thomas via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> One possible problem with this patch, I realize now, is that if you
>> navigate backward ('l') and then visit another link there, the new page
>> is added to the very end of history rather than the immediate next
>> position. This would be confusing if you, then, navigate back and find
>> that it's not the page from which you followed the link. Perhaps the
>> original code was a hack around this?
I intentionally chose not to address this in my patch (though perhaps
that's not the right call).
> The only reasonable alternative is to throw away all the history after
> 'l', which I don't think is better.
>
> What do other browsers do in this situation?
They throw away any history after the page you clicked the link on
(which I think is what you mean by the above).
Another option might be, "If you're at a historical page and you click a
link, add that page as a duplicate to the end of the history." That
would partially restore the old behavior, but only in this case where
things might otherwise be confusing.
We could also add a user option to select between these behaviors, since
the former is the de facto standard for browsers.
(I think the real fix would be something like a history *tree*, but
that's probably quite a bit more work.)
next prev parent reply other threads:[~2024-02-24 22:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 4:59 bug#69232: 30.0.50; [PATCH] EWW history navigation gets caught in a loop Jim Porter
2024-02-19 12:12 ` Eli Zaretskii
2024-02-19 18:55 ` Jim Porter
2024-02-19 19:17 ` Eli Zaretskii
2024-02-22 13:22 ` Eli Zaretskii
2024-02-22 17:18 ` Jim Porter
2024-02-22 19:04 ` Eli Zaretskii
2024-02-22 20:10 ` Jim Porter
2024-02-22 20:13 ` Eli Zaretskii
2024-02-24 14:15 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-24 14:20 ` Eli Zaretskii
2024-02-24 22:29 ` Jim Porter [this message]
2024-02-25 0:50 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-24 22:34 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 5:57 ` Eli Zaretskii
2024-02-25 19:40 ` Jim Porter
2024-02-25 19:49 ` Eli Zaretskii
2024-02-25 22:41 ` Jim Porter
2024-02-28 23:39 ` Jim Porter
2024-02-29 7:03 ` Eli Zaretskii
2024-02-29 17:32 ` Jim Porter
2024-02-29 23:30 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 1:00 ` Jim Porter
2024-03-01 2:10 ` Jim Porter
2024-03-01 7:26 ` Eli Zaretskii
2024-03-01 20:13 ` Jim Porter
2024-03-02 7:38 ` Eli Zaretskii
2024-03-07 0:26 ` Jim Porter
2024-03-01 8:50 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 11:56 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b643f144-1cea-4685-d4c1-624580bb708c@gmail.com \
--to=jporterbugs@gmail.com \
--cc=69232@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jimjoe@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).