From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jim Porter Newsgroups: gmane.emacs.bugs Subject: bug#69232: 30.0.50; [PATCH] EWW history navigation gets caught in a loop Date: Sat, 24 Feb 2024 14:29:21 -0800 Message-ID: References: <8013cc7e-d5de-b793-261f-4b34fbdf360e@gmail.com> <864je4r6ug.fsf@gnu.org> <86y1bc1vn1.fsf@gnu.org> <557131a7-d400-cba5-2b0e-7ec99e8d7fc2@gmail.com> <86sf1k1fss.fsf@gnu.org> <969e4621-fd6f-48cb-2aef-d265971dd56a@gmail.com> <87r0h2x816.fsf@outlook.com> <8634tiymd4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36364"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 69232@debbugs.gnu.org To: Eli Zaretskii , James Thomas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Feb 24 23:37:04 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1re0dk-0009EV-3a for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 24 Feb 2024 23:37:04 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1re0dN-0000pX-RR; Sat, 24 Feb 2024 17:36:41 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1re0dK-0000kJ-Pt for bug-gnu-emacs@gnu.org; Sat, 24 Feb 2024 17:36:38 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1re0dK-0000ee-IM for bug-gnu-emacs@gnu.org; Sat, 24 Feb 2024 17:36:38 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1re0di-0000Iy-Hz for bug-gnu-emacs@gnu.org; Sat, 24 Feb 2024 17:37:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Jim Porter Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 24 Feb 2024 22:37:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 69232 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 69232-submit@debbugs.gnu.org id=B69232.17088142211165 (code B ref 69232); Sat, 24 Feb 2024 22:37:02 +0000 Original-Received: (at 69232) by debbugs.gnu.org; 24 Feb 2024 22:37:01 +0000 Original-Received: from localhost ([127.0.0.1]:37241 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1re0dg-0000Ii-Rf for submit@debbugs.gnu.org; Sat, 24 Feb 2024 17:37:01 -0500 Original-Received: from mail-pl1-f170.google.com ([209.85.214.170]:49160) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1re0de-0000IF-MN for 69232@debbugs.gnu.org; Sat, 24 Feb 2024 17:36:59 -0500 Original-Received: by mail-pl1-f170.google.com with SMTP id d9443c01a7336-1dc9222b337so1489085ad.2 for <69232@debbugs.gnu.org>; Sat, 24 Feb 2024 14:36:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708814128; x=1709418928; darn=debbugs.gnu.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to; bh=+IihduRrOFFN5GF1EOnlDRgF0Cb7efTODvnoXAtVB5Q=; b=Mfog3VKyb5issiDyKOLdAILTp2qGGpgDEwvFuS0aY2+xKLCftLjo5Zwd5G9XczjOGH LJWFtXaOcsWLwDJqBmdYx55vf87c1qbAmDewHGCR+S30PjTsvLZ6P3QAWw1Z7y5/fEcw HhydCp2WXhTtcrCSzz5kGy7Oa2RPvBYKM05igoMfeli0lCtepNy/UqiRE7pfc5kjZOLE DsinDPPA5OCFP7q0yXQ4oKuGY+wywJGwMRDgu+vKW1waqN78gTN5dh43bEzPNcm2UGZx nDjzE+q4wBvgRc5kFjeZrmlhzNS5l1NZ68wl+xdzUQIeLDrWUKUnso8eD0gmpxJxkhfo wjJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708814128; x=1709418928; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+IihduRrOFFN5GF1EOnlDRgF0Cb7efTODvnoXAtVB5Q=; b=RmQflFzl8H16YC9jbtr/0NACfJrjYc7y3IkkezguHyFTFao5JR2/7G3e1SGrCidYfj Hu9hb9YArw4s0+rtle6aEKlm+sLE4nVi81WhloBy1erYCG1sDcdzVHMQiU88QhDEU1Vz L2eRScSOeTbYUwa8WWChpsdClFv020rr2gK0yuQcrRpx1XMO/dX4yjNixW8n6PzV3/Ea jctOYRAXtq+6A34OQNCz2dxnGT98ph4pWEMAuQyrNxmQYu4OLrT8TabUef1low6rKBwS KlyFX74eNTkpFYMLQI85lFmXF4Xcc41ww4W/jJZm6Bnlxx0by5i8MF4DoORMaKtCnN8n Z7fw== X-Gm-Message-State: AOJu0Yw9Ec5p/21dv8Wgm4m3P9oXDx+Kk1vPxrCwWSLLQhIWsc7r4t5F s7qyBROAC4o5prSpjyAGOz8WuFh5KyG4EW5dRwN679J57BPy1MdRbTFrQ6Go X-Google-Smtp-Source: AGHT+IF7APeMPe9mbhoE/PrM/7bwGB52svIVkvEGM74a/dlDu6EwRI5gjvi5BZ/LFOP82RbS+7bwgw== X-Received: by 2002:a05:6a20:b721:b0:1a0:cc37:f850 with SMTP id fg33-20020a056a20b72100b001a0cc37f850mr3267159pzb.36.1708813763588; Sat, 24 Feb 2024 14:29:23 -0800 (PST) Original-Received: from [192.168.1.2] (076-168-148-233.res.spectrum.com. [76.168.148.233]) by smtp.googlemail.com with ESMTPSA id i4-20020a632204000000b005dc26144d96sm1516936pgi.75.2024.02.24.14.29.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 24 Feb 2024 14:29:22 -0800 (PST) Content-Language: en-US In-Reply-To: <8634tiymd4.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:280579 Archived-At: 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" >> >> 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.)