- Dillo-dev - lists.mailman3.com

Re: [PATCH] Middle-click on back button to open prev. page in new tab

by a1ex＠dismail.de

Hi Rodrigo, Rodrigo Arias <rodarima(a)gmail.com> wrote: > Keep in mind that you can right-click the back or forward buttons to > open a list of pages, and middle click any to open them in new tabs. > Not sure if this already fits your needs: > > https://dillo-browser.github.io/user_help.html#history Lol, this is true! I seem to have a real knack for "fixing" non-existent problems :) But, I think it's still useful to have, since now the action can be performed with just 1 click, instead of 2. Also browsers like Firefox offer the middle-click back feature like this, so it might be more intuitive for some users. Regards, Alex

April 27, 2025

Re: [PATCH] Middle-click on back button to open prev. page in new tab

by Rodrigo Arias

Hi Alex, On Sun, Apr 27, 2025 at 10:23:37AM +0200, a1ex(a)dismail.de wrote: >Hi list, > >Hope you are all doing well! > >I have a small feature idea: > >Sometimes I want to go back to the previous page, but also keep the >current page open. > >Obviously I can go back and then open the last page in a new tab, but >that can be annoying having to find and click on the link again. Keep in mind that you can right-click the back or forward buttons to open a list of pages, and middle click any to open them in new tabs. Not sure if this already fits your needs: https://dillo-browser.github.io/user_help.html#history Best, Rodrigo.

April 27, 2025

[PATCH] Middle-click on back button to open prev. page in new tab

by a1ex＠dismail.de

Hi list, Hope you are all doing well! I have a small feature idea: Sometimes I want to go back to the previous page, but also keep the current page open. Obviously I can go back and then open the last page in a new tab, but that can be annoying having to find and click on the link again. One solution is to make middle-clicking on the back button open the previous page in a new tab. Attached is a working proof-of-concept patch. Any feedback would be welcome! Regards, Alex diff -upr a/src/nav.c b/src/nav.c --- a/src/nav.c Mon Apr 21 21:42:32 2025 +++ b/src/nav.c Sun Apr 27 10:11:36 2025 @@ -447,6 +447,20 @@ void a_Nav_back(BrowserWindow *bw) } /* + * Send the browser back to previous page in new tab + */ +void a_Nav_back_nt(BrowserWindow *bw) +{ + int idx = a_Nav_stack_ptr(bw); + + a_Nav_cancel_expect(bw); + if (--idx >= 0){ + a_UIcmd_set_msg(bw, ""); + a_UIcmd_open_url_nt(bw, a_History_get_url(NAV_UIDX(bw,idx)), -1); + } +} + +/* * Send the browser to next page in the history list */ void a_Nav_forw(BrowserWindow *bw) diff -upr a/src/nav.h b/src/nav.h --- a/src/nav.h Mon Apr 21 21:42:32 2025 +++ b/src/nav.h Sun Apr 27 10:12:00 2025 @@ -18,6 +18,7 @@ void a_Nav_push(BrowserWindow *bw, const DilloUrl *url const DilloUrl *requester); void a_Nav_repush(BrowserWindow *bw); void a_Nav_back(BrowserWindow *bw); +void a_Nav_back_nt(BrowserWindow *bw); void a_Nav_forw(BrowserWindow *bw); void a_Nav_home(BrowserWindow *bw); void a_Nav_reload(BrowserWindow *bw); diff -upr a/src/ui.cc b/src/ui.cc --- a/src/ui.cc Mon Apr 21 21:42:32 2025 +++ b/src/ui.cc Sun Apr 27 10:13:45 2025 @@ -312,6 +312,8 @@ static void b1_cb(Fl_Widget *wid, void *cb_data) case UI_BACK: if (b == FL_LEFT_MOUSE) { a_UIcmd_back(a_UIcmd_get_bw_by_widget(wid)); + } else if (b == FL_MIDDLE_MOUSE) { + a_UIcmd_back_nt(a_UIcmd_get_bw_by_widget(wid)); } else if (b == FL_RIGHT_MOUSE) { a_UIcmd_back_popup(a_UIcmd_get_bw_by_widget(wid), wid->x(), wid->y() + wid->h()); diff -upr a/src/uicmd.cc b/src/uicmd.cc --- a/src/uicmd.cc Mon Apr 21 21:42:32 2025 +++ b/src/uicmd.cc Sun Apr 27 10:12:30 2025 @@ -868,6 +868,14 @@ void a_UIcmd_back(void *vbw) } /* + * Send the browser back to previous page in a new tab + */ +void a_UIcmd_back_nt(void *vbw) +{ + a_Nav_back_nt((BrowserWindow*)vbw); +} + +/* * Popup the navigation menu of the Back button */ void a_UIcmd_back_popup(void *vbw, int x, int y) diff -upr a/src/uicmd.hh b/src/uicmd.hh --- a/src/uicmd.hh Mon Apr 21 21:42:32 2025 +++ b/src/uicmd.hh Sun Apr 27 10:12:51 2025 @@ -29,6 +29,7 @@ void a_UIcmd_open_url(BrowserWindow *bw, const DilloUr void a_UIcmd_open_url_nw(BrowserWindow *bw, const DilloUrl *url); void a_UIcmd_open_url_nt(void *vbw, const DilloUrl *url, int focus); void a_UIcmd_back(void *vbw); +void a_UIcmd_back_nt(void *vbw); void a_UIcmd_back_popup(void *vbw, int x, int y); void a_UIcmd_forw(void *vbw); void a_UIcmd_forw_popup(void *vbw, int x, int y);

April 27, 2025

Re: Image Redirects on the Wayback Machine

by Rodrigo Arias

Hi, >Thanks, I've poked around there before but not yet invested the time to >study how it all fits together. I hadn't discovered the developer docs >the first time though (I assumed there was only the info that's in >doc/). Well, I'm still not sure if there are any docs covering the >network-related code... There are not many, but you can find some in devdoc/. I should add them somehow to the website as well. Essentially the cache keeps a list of entries for connections in progress. When data is received, the callback for that entry is called to forward the data. But when a redirect is received, currently Dillo navigates to the new URL, as if you typed it in the location bar. What we need to support first is to allow the cache to fetch the new URL instead of changing the root URL of the current document. I believe we can do this by adding a new entry to the cache with the new URL and copying the callback and other related data, or simply reusing the same entry while we update the URL. I took a look at the time but I wasn't able to come up with a quick solution so I didn't look further. I will eventually take a look at it, but feel free to poke with the cache code in the meanwhile. Best, Rodrigo.

March 25, 2025

Re: Image Redirects on the Wayback Machine

by Kevin Koster

On Tue, 25 Mar 2025 00:13:57 +0100 Rodrigo Arias <rodarima(a)gmail.com> wrote: > >"If Dillo requests an image and receives a response containing a > > redirection (i.e., pointing to a different URL), the redirection is > > not followed. These have a strong tendency to be advertisements." > > https://dillo-browser.github.io/old/FAQ.html#q28 > > > >However it's a real pain since most of the good stuff on the Web > >seems to have gone offline. ~/.dillo/domainrc was added to solve > >similar problems with over-active blocking of images at different > >domains (next part of that FAQ answer). Could some sort of allow > >rule for image redirects be added in that too? Or is there an > >existing work-around for the Wayback Machine images that I > >haven't figured out? > > It is not implemented yet: > > https://github.com/dillo-browser/dillo/issues/304#issuecomment-2486646504 Oh right, I saw that but thought it must have been something else. In the past I believe it's been considered as intended behaviour rather than a bug (eg. in earlier mailing list discussions which I can't find now). Hence my suggestion of a domainrc type whitelist rather than an outright 'fix'. > See Cache_redirect() in src/cache.c if you want to take a look. Thanks, I've poked around there before but not yet invested the time to study how it all fits together. I hadn't discovered the developer docs the first time though (I assumed there was only the info that's in doc/). Well, I'm still not sure if there are any docs covering the network-related code...

March 25, 2025

Re: Image Redirects on the Wayback Machine

by Rodrigo Arias

Hi, On Tue, Mar 25, 2025 at 09:20:25AM +1100, Kevin Koster wrote: >I keep needing to open pages at the Wayback Machine in Links >(graphical mode) because Dillo won't load images there. I know this >is because a while ago they started using redirects on the image >links in their archived pages, and the old Dillo FAQ says: > >"If Dillo requests an image and receives a response containing a > redirection (i.e., pointing to a different URL), the redirection is > not followed. These have a strong tendency to be advertisements." > https://dillo-browser.github.io/old/FAQ.html#q28 > >However it's a real pain since most of the good stuff on the Web >seems to have gone offline. ~/.dillo/domainrc was added to solve >similar problems with over-active blocking of images at different >domains (next part of that FAQ answer). Could some sort of allow >rule for image redirects be added in that too? Or is there an >existing work-around for the Wayback Machine images that I >haven't figured out? It is not implemented yet: https://github.com/dillo-browser/dillo/issues/304#issuecomment-2486646504 See Cache_redirect() in src/cache.c if you want to take a look. Best, Rodrigo.

March 24, 2025

Image Redirects on the Wayback Machine

by Kevin Koster

I keep needing to open pages at the Wayback Machine in Links (graphical mode) because Dillo won't load images there. I know this is because a while ago they started using redirects on the image links in their archived pages, and the old Dillo FAQ says: "If Dillo requests an image and receives a response containing a redirection (i.e., pointing to a different URL), the redirection is not followed. These have a strong tendency to be advertisements." https://dillo-browser.github.io/old/FAQ.html#q28 However it's a real pain since most of the good stuff on the Web seems to have gone offline. ~/.dillo/domainrc was added to solve similar problems with over-active blocking of images at different domains (next part of that FAQ answer). Could some sort of allow rule for image redirects be added in that too? Or is there an existing work-around for the Wayback Machine images that I haven't figured out? Example: The image link at the top of this archived webpage: http://web.archive.org/web/20001009182503/http://www.abc.net.au/defaultlo.h… http://web.archive.org/web/20001009182503im_/http://www.abc.net.au/img/abcb… Redirects to: http://web.archive.org/web/20000822094140im_/http://www.abc.net.au/img/abcb… which isn't loaded unless opened on its own via the right-click menu in Dillo.

March 24, 2025

Re: FOSDEM 2025 video

by Rodrigo Arias

On Sun, Feb 09, 2025 at 01:07:32PM +0200, Schimon Jehudah wrote: >Congratulations! > >That was an interesting idea to present the slideshows via Dillo. > >What key bindings did you use to navigate? I used a custom patch to navigate to the next fragment (div). Still needs some polishing before I can merge it. Rodrigo.

Feb. 9, 2025

FOSDEM 2025 video

by Rodrigo Arias

Hi, I published a custom edit of the FOSDEM 2025 Dillo talk with the colors corrected and a black frame here: https://www.youtube.com/watch?v=sFJp8JDg8Yg It is also on the archive: https://archive.org/details/dillo-fosdem-2025 The official video was just published now: https://fosdem.org/2025/schedule/event/fosdem-2025-4100-resurrecting-the-mi… Best, Rodrigo.

Feb. 9, 2025

Re: Typos Dillo

by Rodrigo Arias

On Tue, Feb 04, 2025 at 10:59:14PM +0100, Rodrigo Arias wrote: >Thanks, they look good. I will merge it with the corrections below >[...] Merged: https://github.com/dillo-browser/dillo/commit/6cd133d2f242d36bd48ddea44acd8… Best, Rodrigo.

Feb. 5, 2025