Notices by Dillo browser (dillo@fosstodon.org), page 2

@lanodan @drewdevault that may work, but I would like to stop using GitHub entirely.

Sr.ht has the benefit it can be mostly used from Dillo itself unlike many other forges.

@drewdevault one of the main reasons we are still on GitHub is that we cannot test Dillo on Mac and Windows on builds.sr.ht (at least not easily).

Context: https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3CC3ZF0IF242P4.3JN5FF60I1J20@keymaker.local%3E

We try to support Dillo on proprietary systems too so that users that may not know yet other OS can learn how to escape by reading the Web, when provided with a browser that runs well on old hardware.

When you remove JavaScript, what continues to work?

Made a simple classification with badges here: https://dillo-browser.github.io/pec/

Any thoughts? (I'm not an expert in graphic design, I know)

Testing new zoom feature on HN

@amarok well, those are known "limitations". An important fraction of pages just display a "I won't do anything until you enable JS and cookies" message.

On the other hand, I saw a case where renderer is failing to handle a very specific case on a page with floats, which should be easy to solve.

Today I tested #Dillo with a list of the top 10K sites and none managed to crash the browser :blobcatcool:

It revealed some other issues though :blobcat_glitch:

@peterkotrcka I cannot reproduce it on Arch with FLTK 1.3.9-1 and i3. Could you open an issue with step by step instructions to try to reproduce it?

@peterkotrcka thanks! It may be related with the way to open the menu or the things previous to that point that is causing me to not be able to reproduce it. Even if it is present in previous versions, we should fix it anyway.

@peterkotrcka yeah, that is expected as it is issuing a reload that writes the last url back in the location bar. Thanks for the videos, they are very good to see what is going on :-)

@peterkotrcka haha, maybe there is a problem there, but only shows from time to time.

Anyway, thanks for testing :-)

@peterkotrcka aah, you are using Wayland?

@peterkotrcka I didn't tested it on Wayland, so probably that's why it never happened to me. I'll open an issue to test it and see if I can reproduce it.

@peterkotrcka I opened this issue to track it down:

https://github.com/dillo-browser/dillo/issues/153

On HackerNews: https://news.ycombinator.com/item?id=40260035

Here is how HN front page looks from #Dillo now.

They just fixed a CSS bug that was causing most rules to be ignored that we discovered this morning.

Dillo 3.1.0 finally released after 9 years!

https://dillo-browser.github.io/latest.html

#Dillo #release

@neauoire @vertigo @jame we are missing a picture of Dillo running on a sailboat :-)

@yeti that's fine.

The limit was in case you are concerned with network usage when browsing, and only what should be the default limit when you enable it (opt-in).

The user should have the ability to choose an arbitrary limit in any case, this is only in case there was some consensus on what would be a reasonable default limit (there is no consensus).

Also, it should be posible to download the rest of the page if requested.

@adele nice! We should add support for CSS rem units.

Monthly commits in #Dillo colored by authors.

Cannot find anywhere the 2002-2008 CVS repo (was at cvs.auriga.wearlab.de), when it switched from sourceforge.