September 2026 - Dillo-dev - lists.mailman3.com

[PATCH] Prevent DilloPlain::write() from reading past end of buffer
by 256＠256-32.com Oct. 21, 2026

Oct. 21, 2026

In src/plain.cc, \r\n sequences are handled with these lines: while ( i < MaxBytes ) { ... addLine(Start + i - len, len); if (Start[i] == '\r' && Start[i + 1] == '\n') ++i; if (i < MaxBytes) ++i; ... So if a \r occurs, skip over the \n if present. But if i + 1 == MaxBytes, Start[i + 1] is one past the end of the buffer, which is an out-of-bounds read. This happens if a file ends in \r, or I suppose if a file gets broken up and parsed with multiple invocations of the function. I think this could theoretically add a redundant line break to the rendered page. My diff fixes this. I have tested it with \r, \r\n, and \n line endings. I haven't been able to test how it behaves with plaintext pages that are parsed in multiple invocations, though. (Also, and this is unrelated but it bothers me: prefsparser.cc has a comment saying the `symbols` array is sorted, but it isn't.) diff --git a/src/plain.cc b/src/plain.cc index 0f5d6a48..e085ab19 100644 --- a/src/plain.cc +++ b/src/plain.cc @@ -142,7 +142,10 @@ void DilloPlain::addLine(char *Buf, uint_t BufSize) { int len; char buf[129]; - char *end = Buf + BufSize; + char *end; + + if (BufSize > 0 && Buf[BufSize - 1] == '\r') --BufSize; + end = Buf + BufSize; currentLine++; /* Start at 1 */ sprintf(buf, "L%ld", currentLine); /* Always fits */ @@ -181,7 +184,8 @@ void DilloPlain::write(void *Buf, uint_t BufSize, int Eof) while ( i < MaxBytes ) { switch ( state ) { case ST_SeekingEol: - if (Start[i] == '\n' || Start[i] == '\r') + if (Start[i] == '\n' || (Start[i] == '\r' && i + 1 < MaxBytes + && Start[i + 1] != '\n')) state = ST_Eol; else { ++i; ++len; @@ -189,8 +193,7 @@ void DilloPlain::write(void *Buf, uint_t BufSize, int Eof) break; case ST_Eol: addLine(Start + i - len, len); - if (Start[i] == '\r' && Start[i + 1] == '\n') ++i; - if (i < MaxBytes) ++i; + ++i; state = ST_SeekingEol; len = 0; break;

2 4

How minimalist should Dillo be?
by 256＠256-32.com Oct. 17, 2026

Oct. 17, 2026

I want to improve Dillo in a bunch of ways, most urgently by adding support for the "expires" HTTP header field, and improving the HTML/CSS rendering. I'm worried, though, that if I submit a huge patch to do one of these things it'd get rejected for not being minimalist enough. DilloNG (which is abandoned) and Dillo+ are both hosted on GitHub, and I'd rather not use that site. I don't want to fork the browser and deal with all the overhead of hosting and distribution. And I definitely don't want to write my own browser from scratch. My question is, would substantially fleshing out the layout and style engines be seen as going against the spirit of Dillo? Would it push too far against the 1.44MB limit?

3 4

[PATCH 0/2] Fix crashes seen on subpages of https://www.pythontutorial.net/
by Andreas Kemnade Oct. 11, 2026

Oct. 11, 2026

There are input type="button" without value there, do not crash. The main repo seems not to have a pull request functionality, so I am using the good old git format-patch way, so it can be applied via git am. Andreas Kemnade (2): do not crash at input tags which do neither produce resources or embeds form input: try to find defaults for buttons without a value src/form.cc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) -- 2.47.3

2 4

Rendering math in Wikipedia
by Ethan James Sue Sept. 22, 2026

Sept. 22, 2026

Dear fellow Dillo users, When math equations are rendered in Wikipedia, they seem to render three times. For example, in the attached screenshot, it says "p i", then the markdown "{\displaystyle p^{i}}", and then the image. I see that SVG support for Wikipedia math formulas was added in 2025, so I wonder if this is a known issue with a workaround. Any advice would be appreciated! Ethan

2 2

Segfault when loading web site
by Ben Collver Sept. 22, 2026

Sept. 22, 2026

Good day, Dillo crashes when i open https://www.masterbrandcabinets.com/ $ dillo --version Dillo v3.3.0 Libraries: fltk/1.3.8 jpeg/2.1.2 png/1.6.58 webp/1.3.2 zlib/1.2.13 brotli/1.0.9 OpenSSL/1.1.1zh Features: +GIF +JPEG +PNG +SVG +WEBP +BROTLI +XEMBED +TLS +IPV6 +CTL $ dillo https://www.masterbrandcabinets.com/ ... NumPendingStyleSheets=8 NumPendingStyleSheets=9 NumPendingStyleSheets=10 Segmentation fault Best regards, -Ben

2 3

link element is conditionally allowed in body
by Andrea Pappacoda Sept. 14, 2026

Sept. 14, 2026

Hi again :) I noticed another incorrect warning from the bug meter, triggered by https://hackinpovo.it, this time saying: This <link> element must be inside the HEAD section. Which is not true. Citing the HTML spec. From both <https://html.spec.whatwg.org/review-drafts/2020-01/#allowed-in-the-body> and <https://html.spec.whatwg.org/dev/semantics.html#allowed-in-the-body>, > If a link element has an itemprop attribute, or has a rel attribute > that contains only keywords that are body-ok, then the element is said > to be allowed in the body. From both <https://html.spec.whatwg.org/review-drafts/2020-01/#body-ok> and <https://html.spec.whatwg.org/dev/links.html#body-ok>, > The body-ok keywords are dns-prefetch, modulepreload, pingback, > preconnect, prefetch, preload, and stylesheet. Not ideal, I agree, but that's what it says :/

1 0

Bogus "required DOCTYPE declaration is missing" in XHTML
by Andrea Pappacoda Sept. 14, 2026

Sept. 14, 2026

Hi! I just noticed that my website, andrea.pappacoda.it, triggers a warning from the bug meter: HTML warning: line 1, The required DOCTYPE declaration is missing. Handling as HTML4. My website though is an XHTML page, served with the application/xhtml+xml media type, and thus requires no DOCTYPE, which is only required in the "HTML syntax" of HTML. See: - https://html.spec.whatwg.org/dev/xhtml.html#the-xhtml-syntax - https://html.spec.whatwg.org/dev/syntax.html#syntax I couldn't find a way to add this to the bug tracker, so I'm sending it here. Please keep me Cc'd as I'm not subscribed :) Bye!

1 0

[PATCH] Fix build on GNU/hurd via dynamic allocation
by João Pedro Malhado Sept. 1, 2026

Sept. 1, 2026

Dear Dillo Maintainers, I noticed that the Dillo 3.3.0 Debian package build was failing on GNU/hurd due to the PATH_MAX macro not being defined on that platform. This is a common portability issue on the platform, and the following page indicates why the macro is not defined in GNU/hurd https://www.gnu.org/software/hurd/faq/foo_max It was pointed out to me that commit b43ab26e81a1e399e3cb148b972a284518aa4d39 has addressed the hurd build failure already, but it does so by simply defining PATH_MAX to an arbitrary value. As per the page above, the preferred way to address the issue by allocating the size of the path dynamically. I submit the following patch to your consideration. The patch applies to version 3.3.0 of the file present in Debian, before the above mentioned commit. Best regards, João

2 3