- Dillo-dev - lists.mailman3.com

Re: "Segmentation fault" after pressing a button on a website

by Rodrigo Arias

Hi, On Mon, Mar 09, 2026 at 04:19:27PM -0300, Juan M Sevilla wrote: >Hi, > >9 mar. 2026 11:50:34 a1ex(a)dismail.de: >>I believe the problem is related to this known issue: >> >>https://bug.dillo-browser.org/506/ >> >>It is possible to work around it for now by putting something like >>this in your ~/.dillo/style.css file: >> >>select { display: inline !important; } > >Oh, I see, thank you! I should've checked the bug tracker —it was >quite late last night. > >I'll try that workaround meanwhile, thanks! I pushed a patch that hopefully fixes it: https://git.dillo-browser.org/dillo/log/?h=fix-hidden-form Let me know if you encounter any other page that segfaults when submitting a form, so far it seems to be working fine in my tests. Best, Rodrigo.

March 21, 2026

Re: [Issue]: Web search prefix lenght

by Rodrigo Arias

Hi Juan, On Mon, Mar 09, 2026 at 12:07:49AM -0300, Juan M Sevilla wrote: >Hi, apologies for the delay and thanks for the clarification. The patch >works as expected! I tested with more than 20 search engines and >everything behaves correctly. Thank you very much! > >Luckily, I started learning more about using git last weekend, so >learning to change branch to compile was like a good exercise :) Thanks for the tests. Merged: https://git.dillo-browser.org/dillo/commit/?id=da1819ce6e2efb71f71c753cddf6… Best, Rodrigo.

March 16, 2026

Re: "Segmentation fault" after pressing a button on a website

by Juan M Sevilla

Hi, 9 mar. 2026 11:50:34 a1ex(a)dismail.de: > I believe the problem is related to this known issue: > > https://bug.dillo-browser.org/506/ > > It is possible to work around it for now by putting something like > this in your ~/.dillo/style.css file: > > select { display: inline !important; } Oh, I see, thank you! I should've checked the bug tracker —it was quite late last night. I'll try that workaround meanwhile, thanks! Kind regards

March 9, 2026

Re: "Segmentation fault" after pressing a button on a website

by a1ex＠dismail.de

Hi, Juan M Sevilla <jumase+dillo(a)disroot.org> wrote: > Hi, while testing search engines, I found that on this particular site > https://paulina.toolforge.org/, when you press the button to submit > your search, Dillo crashes with the following message on the terminal: > "Violación de segmento". I believe the problem is related to this known issue: https://bug.dillo-browser.org/506/ It is possible to work around it for now by putting something like this in your ~/.dillo/style.css file: select { display: inline !important; } Regards, Alex

March 9, 2026

"Segmentation fault" after pressing a button on a website

by Juan M Sevilla

Hi, while testing search engines, I found that on this particular site https://paulina.toolforge.org/, when you press the button to submit your search, Dillo crashes with the following message on the terminal: "Violación de segmento". Here are the logs I get: > Nav_open_url: new url='https://paulina.toolforge.org/' > Dns_server [0]: paulina.toolforge.org is 2a02:ec80:a000:1::2bc > 185.15.56.88 Connecting to [2a02:ec80:a000:1::2bc]:443 > paulina.toolforge.org: TLSv1.3, cipher TLS_AES_256_GCM_SHA384 > 0: ecdsa-with-SHA384 256-bit EC: /CN=toolforge.org > 1: sha256 384-bit EC: /C=US/O=Let's Encrypt/CN=E8 > root: /C=US/O=Internet Security Research Group/CN=ISRG Root X1 > NumPendingStyleSheets=1 > NumPendingStyleSheets=2 > NumPendingStyleSheets=3 > Dns_server [0]: tools-static.wmflabs.org is 2a02:ec80:a000:1::1d > 185.15.56.49 tools-static.wmflabs.org: TLSv1.3, cipher > TLS_AES_256_GCM_SHA384 0: ecdsa-with-SHA384 256-bit EC: > /CN=wmcloud.org 1: sha256 384-bit EC: /C=US/O=Let's Encrypt/CN=E8 > root: /C=US/O=Internet Security Research Group/CN=ISRG Root X1 > >>>> a_Nav_repush <<<< > Nav_open_url: new url='https://paulina.toolforge.org/' > a_Nav_expect_done: repush! > Violación de segmento It happens on both Dillo branches "master" and "match-prefix-exactly" $ dillo -v Dillo Libraries: fltk/1.3.11 jpeg/2.1.5 png/1.6.48 webp/1.5.0 zlib/1.3.1 OpenSSL/3.5.4 Features: +GIF +JPEG +PNG +SVG +WEBP -BROTLI +XEMBED +TLS +IPV6 -CTL

March 9, 2026

Re: [Issue]: Web search prefix lenght

by Juan M Sevilla

On Mon, 2 Mar 2026 20:25:54 +0100 Rodrigo Arias wrote: > There is no character limit but Dillo matches the first search entry > that starts with the prefix. So "wi" will match both "wi" and "wien". > The first match is used. > > One option is to use prefixes that are not substrings of other > prefixes (like wes and wen). > > I think it makes sense to change the behavior to match only the > complete prefix, as the user can write the shortened version > manually. So that "wi" won't match "wien", but only "wi". > > I uploaded the patch here: > > https://git.dillo-browser.org/dillo/log/?h=match-prefix-exactly > > Let me know if that works for your. Hi, apologies for the delay and thanks for the clarification. The patch works as expected! I tested with more than 20 search engines and everything behaves correctly. Thank you very much! Luckily, I started learning more about using git last weekend, so learning to change branch to compile was like a good exercise :) Best regards

March 9, 2026

Always show tab-bar

by a1ex＠dismail.de

Hi, I have added a section to my Dillo patches blog post about modding the tab-bar: https://alex.envs.net/blog/dillo/ Basically, I think it would be nice to have an option to always show the tab-bar. Is there any interest in such a feature? Regards, Alex

March 5, 2026

Re: [Issue]: Web search prefix lenght

by Rodrigo Arias

Hi, On Sun, Mar 01, 2026 at 06:47:12PM -0300, Juan M Sevilla wrote: >Hi, I'm using prefixes to search using different websites, but noticed >that this prefix cannot be 1 nor more than 2 characters long. > >For example, I configured Wikipedia in English and Spanish, the former >with prefix "wien" and the latter just "wi". In my dillorc, the English >version is first, so Dillo always uses this one to search, whether I >type "wi hola" or "wien hola". > >I've also set a dictionary with prefix "d", but Dillo always searches >on DuckDuckGo, which has the prefix "dd". > >I wonder if prefixes could be longer or shorter. On Firefox, I'm using >from 1 to 4 characters, the longer ones mainly to differentiate the >English from the Spanish version (Wikipedia; Wiktionary; WordReference >Translate, Dictionaries, Synonim). There is no character limit but Dillo matches the first search entry that starts with the prefix. So "wi" will match both "wi" and "wien". The first match is used. One option is to use prefixes that are not substrings of other prefixes (like wes and wen). I think it makes sense to change the behavior to match only the complete prefix, as the user can write the shortened version manually. So that "wi" won't match "wien", but only "wi". I uploaded the patch here: https://git.dillo-browser.org/dillo/log/?h=match-prefix-exactly Let me know if that works for your. >Otherwise, I can live with the 2-character length, but it would be >great if it was stated on the dillorc file, something like: > >> (the prefix serves to search from the Location Bar. e.g. "dd dillo >> image" and it must be 2 characters long) > >Thank you! I've been using Dillo for six months and I like it very >much :D Glad to read that :) Best, Rodrigo.

March 2, 2026

[Issue]: Web search prefix lenght

by Juan M Sevilla

Hi, I'm using prefixes to search using different websites, but noticed that this prefix cannot be 1 nor more than 2 characters long. For example, I configured Wikipedia in English and Spanish, the former with prefix "wien" and the latter just "wi". In my dillorc, the English version is first, so Dillo always uses this one to search, whether I type "wi hola" or "wien hola". I've also set a dictionary with prefix "d", but Dillo always searches on DuckDuckGo, which has the prefix "dd". I wonder if prefixes could be longer or shorter. On Firefox, I'm using from 1 to 4 characters, the longer ones mainly to differentiate the English from the Spanish version (Wikipedia; Wiktionary; WordReference Translate, Dictionaries, Synonim). Otherwise, I can live with the 2-character length, but it would be great if it was stated on the dillorc file, something like: > (the prefix serves to search from the Location Bar. e.g. "dd dillo > image" and it must be 2 characters long) Thank you! I've been using Dillo for six months and I like it very much :D

March 1, 2026

FLTK 1.4 experimental support

by Rodrigo Arias

Hi, I pushed the fltk-1.4 branch to support building dillo with FLTK >= 1.4. It needs the configure flag --enable-experimental-fltk: https://git.dillo-browser.org/dillo/log/?h=fltk-1.4 The objective is to allow early adopters to build dillo so we can unblock the next 3.3.0 release. There are known problems with scrolling and with font hinting and antialiasing which I will be focusing later. For know I'm interested in testing that dillo can build correctly with FLTK 1.4 on different platforms. To build, use this with the path to fltk-config binary of FLTK 1.4: % ../configure --enable-experimental-fltk FLTK_CONFIG=/.../fltk-config Or manually specify the flags with FLTK_CFLAGS, FLTK_CXXFLAGS and FLTK_LIBS variables. Dillo should report the FLTK version: % dillo -v Dillo v3.2.0-162-g6142b99f Libraries: fltk/1.4.4 jpeg/3.1.2 png/1.6.53 webp/1.6.0 zlib/1.3.1 brotli/1.1.0 OpenSSL/3.6.0 Features: +GIF +JPEG +PNG +SVG +WEBP +BROTLI +XEMBED +TLS +IPV6 +CTL Let me know if you encounter any problems during the build. Patches that solve rendering problems are very much welcome. Best, Rodrigo.

Feb. 22, 2026