- Dillo-dev - lists.mailman3.com

[PATCH] Fix display of disabled options in configure.ac
by a1ex＠dismail.de March 23, 2026

March 23, 2026

Hi, There are a couple of missing variables in configure.ac which result in missing info when disabling some options via configure: Features: Cookies enabled: no XEmbed enabled : no JPEG enabled : no PNG enabled : no GIF enabled : no SVG enabled : no WEBP enabled : Brotli enabled : IPv6 enabled : no Control socket : no (experimental) We are missing variables for WEBP and Brotli. The attached patch fixes this. Regards, Alex

2 1

"Segmentation fault" after pressing a button on a website
by Juan M Sevilla March 23, 2026

March 23, 2026

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

3 5

Preparation for Dillo 3.3.0 release
by Rodrigo Arias March 22, 2026

March 22, 2026

Hi, As most blockers for the release are now solved, I would like to start preparing the 3.3.0 release, which will be the first to include experimental support for FLTK 1.4. It must be manually enabled with the --enable-experimental-fltk configure flag and is only recommended for early testers or developers. Please, let me know if there is any patch that you have planned to get merged before the release. Best, Rodrigo.

1 0

[Issue]: Web search prefix lenght
by Juan M Sevilla March 16, 2026

March 16, 2026

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

2 3

Always show tab-bar
by a1ex＠dismail.de March 5, 2026

March 5, 2026

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

1 0

FLTK 1.4 experimental support
by Rodrigo Arias Feb. 22, 2026

Feb. 22, 2026

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.

1 0

[PATCH] Use FL_FOREGROUND_COLOR for widget selection color
by a1ex＠dismail.de Feb. 20, 2026

Feb. 20, 2026

Hi, Currently Dillo uses a fixed color (black) for the widget selection color, which includes checkmarks and radio buttons. When using a dark color scheme, these selections can be invisible or hard to see. Instead, use the foreground color from dillorc to ensure visibility. Patch is attached. Also, I put up a little blog post with some other Dillo patches, hopefully someone here will find it interesting! I welcome any feedback. https://alex.envs.net/blog/dillo Regards, Alex

2 1

Patches for two use-after-free bugs
by Nopey Nope Feb. 1, 2026

Feb. 1, 2026

Hello! Find attached two patches, which each fix a use-after-free bug. I've also attached a crashing html document for each, but please be aware that these reproducer documents link urls from external web servers. The reproducers crash reliably on my x86_64 Void Linux laptop, but I've not tested them elsewhere. I've also attached a crash log with asan reporting of each. Thank you -Magnus L p.s. I've also opened github PR 449 with these same changes, but figured I should send the patches via email as well-- if only for practice :)

2 4

Segfault while running SSL Labs CurveBall test
by a1ex＠dismail.de Jan. 16, 2026

Jan. 16, 2026

Hi, I was running some tests from ssllabs.com and ran into a segfault. I used the "CurveBall" manual test link from this page: https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html Which points to: https://www.ssllabs.com:10446/ Nav_open_url: new url='https://www.ssllabs.com:10446/' Connecting to 69.67.183.100:10446 www.ssllabs.com:10446: TLSv1.2, cipher ECDHE-ECDSA-AES256-GCM-SHA384 ecdsa-with-SHA256 384-bit EC: /C=US/ST=California/L=Foster City/O=Qualys, Inc./OU=SSLLabs CurveBall Leaf/CN=www.ssllabs.com ecdsa-with-SHA256 Program received signal SIGSEGV, Segmentation fault. _lcry_EVP_PKEY_id (pkey=0x0) at /usr/src/lib/libcrypto/evp/p_lib.c:793 793 return pkey->type; (gdb) bt #0 _lcry_EVP_PKEY_id (pkey=0x0) at /usr/src/lib/libcrypto/evp/p_lib.c:793 #1 0x000001f9ee7da2b0 in Tls_check_cert_strength (ssl=<optimized out>, srv=<optimized out>, choice=0x6faff21f66f8) at tls_openssl.c:526 #2 0x000001f9ee7d8fd3 in Tls_examine_certificate (ssl=0x1fca8ddac80, srv=0x1fc1b4056a0) at tls_openssl.c:865 #3 Tls_connect (fd=7, connkey=4) at tls_openssl.c:1208 #4 0x000001fce9a7a7f0 in fl_wait(double) () from /usr/local/lib/libfltk.so.9.0 #5 0x000001fce9a0777f in Fl::wait(double) () from /usr/local/lib/libfltk.so.9.0 #6 0x000001fce9a079a1 in Fl::wait() () from /usr/local/lib/libfltk.so.9.0 #7 0x000001f9ee77e774 in main (argc=1, argv=0x6faff21f6a48) at dillo.cc:621 When I try to open it with curl, this is the result: curl: (35) TLS connect error: error:10FFF010:elliptic curve routines:CRYPTO_internal:EC lib This is on OpenBSD, using LibreSSL. I did a curl test on a Linux box and didn't get that error, so it may be LibreSSL specific. Happy to do further testing if you have any ideas. Regards, Alex

2 2

Avoid ctype(3) abuses
by Leonardo Taccari Jan. 16, 2026

Jan. 16, 2026

Hello! Most ctype(3) functions usage abuses an undefined behavior of passing values outside integers outside EOF or the range representable as unsigned char. On NetBSD 11 and newer such incorrect behaviors crashes applications violating that and due that Dillo easily crash by just visiting, e.g. <https://www.NetBSD.org/>. For possible further information please give a look to <https://man.NetBSD.org/ctype.3#CAVEATS>. I have grep-ed all such uses and added the relevant cast to uchar_t similar to other ctype(3) calls already present and in that way I can also confirm that Dillo no longer crashes. Attached in this email you can find a patch to address that. Thank you!

2 6