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

Rendering math in Wikipedia

by Ethan James Sue

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

Sept. 20, 2026

link element is conditionally allowed in body

by Andrea Pappacoda

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 :/

Sept. 14, 2026

Bogus "required DOCTYPE declaration is missing" in XHTML

by Andrea Pappacoda

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!

Sept. 14, 2026

[PATCH] Prevent DilloPlain::write() from reading past end of buffer

by 256＠256-32.com

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;

Sept. 10, 2026

Re: [PATCH] Fix build on GNU/hurd via dynamic allocation

by João Pedro Malhado

Hello Rodrigo, Thank you for getting back to me. On Mon, Aug 31, 2026 at 09:02:25PM +0200, Rodrigo Arias wrote: > So I don't see a need for it to be longer than 4096 bytes, but let me know > otherwise. Notice that asprintf() is not portable, is a GNU extension. It is my understanding that asprintf has been added to the POSIX 2024 standard https://pubs.opengroup.org/onlinepubs/9799919799/functions/fprintf.html But if you prefer to avoid it there are off course other ways to achieve the same thing. > The utility of having a compile time limit is to be able to build the > ctlpath in the stack and avoid freeing the heap on errors, as you see in > your 5 extra calls to free(). If your preference is to allocate on the stack that is what is achieved with my first proposed patch at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1146261#5 but it seems that allocation on the heap is usually preferred https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1146261#6 > Having an unbounded path means that any untrusted input path from the user > is potentially a DoS as the path can happily take 1 TiB. It might be worth > reconsidering this decision on GNU/hurd. It is not so much that the path length is unbound, there will be a limit in practice, but the arbitrariness of the value (which often does not actually correspond to a maximum), whether this should be defined at the ABI level and the problems and inconsistencies that arise from it. I am not the best person to to make a convincing argument about this, but others have done, and I don't see GNU/Hurd changing on this (it would be very easy to do so, so the reasons for not doing it hold). How you deal with how Dillo builds on the hurd if off course your call, and thank you for caring about making your software available on this OS. Best regards, João

Sept. 1, 2026