- Dillo-dev - lists.mailman3.com

Dillo not rendering HTML with comments before <!DOCTYPE>

by Kevin Koster

This problem was present in 3.0.5 as well as in 3.1.0-rc1. URL: http://www.lemis.com/ CSS: enabled or disabled Summary: Won't render HTML with comments before <!DOCTYPE>. Pages on this website aren't rendered, just displayed as source code. Although they are XHTML, this doesn't appear to be due to this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036382 If I save the file as lemis.xhtml and remove the two comment lines before the <!DOCTYPE> declaration, then it renders when I load it with file:// or http://, otherwise it doesn't. My reading is that comments there are valid for HTML 4 (which is declared in the page's <!DOCTYPE>) since the standard says: White space (spaces, newlines, tabs, and comments) may appear before or after each section. https://www.w3.org/TR/html401/struct/global.html#h-7.1

April 20, 2024

scroll_step description

by Kevin Koster

There's a new "scroll_step" option in the example configuration file for 3.1.0-rc1. The comment "Mouse wheel scroll step in pixels" suggests that this only affects the mouse wheel, but it also changes the distance the page moves when the arrow keys are pressed and the overlap of previous page content that's left when you press Page Up/Down. I think that's a little confusing, especially as the value has changed since the default behaviour in 3.0.5 (the old value seems to have been about 25).

April 20, 2024

<td> width attributes ignored

by Kevin Koster

Another page rendering issue that's introduced after the 3.0.5 release, this time affecting my own website. URL: http://www.ombertech.com/ CSS: enabled or disabled Summary: <td> width attributes ignored. 3.0.5: Heading table at the top of the page displays correctly scaled with links in the middle formatted in a horizontal row if they all fit in 1/3rd of the browser window's width. 3.1.0-rc1: The "width" attributes of the <td> elements are ignored and the links in the middle are thereby squashed into a vertical row. Further testing with modified versions of the page shows that this table cell width problem is only present if the width attribute in the <td> elements is a percentage and the <table> element also has a width attribute set as a percentage, then the <td> width attributes get ignored. If either (or both) table or td width is in pixels, the problem isn't present, only when table and td width are both specified as percentages. So far as I can tell setting width in <table> and <td> elements as a percentage is valid for HTML 4.01 Transitional, and other browsers (Links, Firefox) render the table correctly.

April 20, 2024

Links closed empty due to <a> containing <div>

by Kevin Koster

I use Dillo 3.0.5 (with SNI support added to the HTTPS plug-in) for the majority of my web browsing, so it's great to see some movement towards the next version. Testing 3.1.0-rc1 I still notice some HTML rendering regressions and other bugs which I'll report in this and the following emails. I don't see any of these the GitHub Issues section, but I won't post them there because I hate the GitHub website - it doesn't work in my favourite web browser for one thing! Other people are welcome to, though I'll only participate in discussion here. URL: http://my-addr.com/ CSS: enabled or disabled Summary: Links closed empty due to <a> containing <div>. 3.0.5: All links on page are usable and <a> elements don't have errors listed in the bug window. 3.1.0-rc1: Links below the horizontal heading bar at the top of the page aren't usable, they're just shown as plain text. The Bug window shows all of these <a> elements are closed when a <div> element is found inside them, leaving no text present inside the link. I see that <div> isn't allowed inside <a> according to the standard, but other browsers (Links and Firefox) still render this website's links in a functional way and it's a pretty inconvenient breakage.

April 20, 2024

DFKOO Order Purchase

by Brumaco Brasil Ltda

April 16, 2024

Re: thank you for dillo

by Rodrigo Arias

Hi Gilbert, On Thu, Apr 11, 2024 at 10:29:32PM +0200, Gilbert Fernandes wrote: > Hello. > > Wanted to thank you for taking care of Dillo. Many years ago I > mostly used OpenBD as operating system and Dillo was my favorite > browser to use there. Making Firefox to work properly on OpenBSD, > in those old times, was not great as I liked to used weird non-x86 > platforms and building Firefox from source.. well. I don't want to > remember that. > > Seen today a link on Hacker News to the new release of Dillo. Made > me smile because I have a very, very fond memory of Dillo. > Everytime I launched my OpenBSD, Dillo was the second software I > would always launch, the first one being, of course, an xterm. > > I did not knew that we lost Sebastian Geerken. To my shame, I > never even checked who wrote Dillo and gave me a working browser > under OpenBSD. I checked your "Donate to Dillo" and seeing that > you have no patron there... :( > > I'm gonna patron Dillo. Won't be a huge amount but I will keep it > running for as long I'm still alive. I no longer use OpenBSD but I > still use Dillo (even if my very modern Fedora has Firefox) and > it's time I give something back to it. > > Thank you for keeping that project alive. Sebastian's memory is > kept by doing so. Thank you for your kind words and for becoming a patron of Dillo. Regards, Rodrigo.

April 12, 2024

thank you for dillo

by Gilbert Fernandes

April 11, 2024

Dillo 3.1.0-rc1 released

by Rodrigo Arias

Hi all, I have uploaded the 3.1.0-rc1 release: https://dillo-browser.github.io/latest.html Download it from GitHub: https://github.com/dillo-browser/dillo/releases/tag/v3.1.0-rc1 Please, test it if you can and report any problems :-) Thanks, Rodrigo.

April 11, 2024

Re: [PATCH] User defined new tab page

by a1ex＠dismail.de

> We may leave the value "about:blank" by default (and forbid ""), but > then, when opening a new tab, if the new_tab_url matches > "about:blank", we set it to NULL to leave the location empty, which > follows the current behavior. Maybe, something like this? > > + if (!url && strcmp(URL_STR(prefs.new_tab_page), "about:blank") != > 0) > + url = prefs.new_tab_page; That does seem like the most elegant solution for now. Thanks! Alex

April 11, 2024

Re: [PATCH] User defined new tab page

by Rodrigo Arias

>I'm looking at lines 401-411 in url.c, and almost have it working as you >suggest. My code is undoubtedly ugly and incorrect, so I might need some >help with this one. Will keep trying. The problem is that the url "" is converted to "http:/" when parsing the value from the preferences. We may leave the value "about:blank" by default (and forbid ""), but then, when opening a new tab, if the new_tab_url matches "about:blank", we set it to NULL to leave the location empty, which follows the current behavior. Maybe, something like this? + if (!url && strcmp(URL_STR(prefs.new_tab_page), "about:blank") != 0) + url = prefs.new_tab_page; So we keep url to NULL when opening "about:blank". >Right, the pre-selection doesn't seem to work with other urls. >I still haven't figured out how to fix that, but am guessing that >as soon as content starts to load, it deselects the text. I think the >feature is still useful given that caveat, but surely there must be >some solution. The selection is lost because of this call that sets the location value: https://github.com/dillo-browser/dillo/blob/c7d5e1e071955b1009b114146014960… I'm thinking if we really want to focus on the location bar when not opening "about:blank" as you may want to load a search engine and focus on the search input instead. I think for now this is not needed, as long as we can keep the current behavior intact by default. We can add another option later to always focus the location bar when is not an empty page. Thanks, Rodrigo.

April 11, 2024