June 2015 - Dillo-dev - lists.mailman3.com

Dillo CPU-hog lock on slashdot
by jcid＠dillo.org 31 Jul '15

31 Jul '15

Hi there, Trying to read about this laptop on slashdot dillo locks with 100% CPU and increasing memory footprint. :-P [1] http://hardware.slashdot.org/story/15/01/20/1655242/librem-a-laptop-custom-… -- Cheers Jorge.-

2 2

Here's 3.0.5 RC1
by eocene＠gmx.com 01 Jul '15

01 Jul '15

In my use of the 3.0.5 branch, there haven't been any unpleasant surprises, so let's have an RC: http://www.dillo.org/download/dillo-3.0.5-rc1.tar.bz2 If it's any comfort to have the sha256sum, it's: 484748e98b263ccd595ce349857edec4a431feb414e44cdbe86722a64387d000

6 7

Dillo version 3.1-dev hangs on http://www.nhl.com
by waltdnes＠waltdnes.org 18 Jun '15

18 Jun '15

I pulled a few minutes ago and built it (8-year-old Intel Core 2 Duo running 64-bit Gentoo linux). It runs OK on CNN.COM and even the NHL mobile site http://m.nhl.com but with most of the tabs not working (Javascript, I assume). However, going to the main NHL site http://www.nhl.com hangs dillo and pegs a CPU. Here's a line of output from "top c", showing 99.2% CPU usage... 19235 waltdnes 20 0 328552 114840 11708 R 99.2 3.7 0:09.89 /home/waltdnes/.local/bin/dillo I have to pop open an xterm window and kill the pid e.g. "kill -3 19235" "dillo -v" shows "Dillo version 3.1-dev" -- Walter Dnes <waltdnes at waltdnes.org>

1 0

splash links
by eocene＠gmx.com 15 Jun '15

15 Jun '15

1. freecode. Between the fact that the site's been in suspended animation for a year and there's been all of this sourceforge unpleasantness just lately, it would be nice not to link to them. 2. In my opinion, it wouldn't do any harm to remove the "News", "Additional Stuff", and "Essential Readings" links, as they have something of an Internet Circa 2002 flavor (in some ways it's a shame to think how pioneering projects like Project Gutenberg lose their preeminence as the pioneer days end, but I suppose that's the way of things). PS Been running on the 3.0.5 branch here, of course, and everything's been fine so far.

2 2

how about if we make a 3.0.5
by eocene＠gmx.com 13 Jun '15

13 Jun '15

It would be nice to put out some new stuff. Primary motivations: 1. placeholder attributes for textarea/input are everywhere, and often they have no other explanation of their purpose. Having to guess "this is probably for search, this is probably for username, this is probably for password" is no fun. 2. I know there are users just trusting dillo's https, so at the least it would be good for their https dpis to have a better cipher list and to disable SSL3 and compression. And then pick out some small, safe fixes. Just to look at ChangeLog, some candidates might be: - Fix crash that's possible searching for text while page still being built. - Fix for segfault when there's no dpid and view source is requested. - Fix view-source dpi to handle null characters correctly. - Made view-source dpi use CSS formatting (it's shorter and cleaner). - Crosscompile/buildroot-friendly fltk-config test. - Fix X11 icon name. - In location bar, tend toward showing beginning of URL instead of end. - Handle irix's version of vsnprintf(). - Fix bug with font_factor preference and CSS font-size:(larger|smaller). - Recognize Menu key in keysrc. - Avoid requesting background images if an ancestor has display:none. - Ignore built-in search url if any are specified in dillorc.

2 4

[jcid@dillo.org: Re: how about if we make a 3.0.5]
by jcid＠dillo.org 12 Jun '15

12 Jun '15

Ooops, I mistakenly replied private... Here's the FWD. -- Cheers Jorge.-

2 3

Google broke recently with 3.0.4 causing repush loop
by dennisn＠dennisn.mooo.com 06 Jun '15

06 Jun '15

This past week or so Google (main search site, image.google) broke for me -- Dillo (3.0.4) goes into an endless "repush" loop: Nav_open_url: new url='http://images.google.com/images?q=bra' Dns_server [0]: images.google.com is 96.127.250.44 96.127.250.42 96.127.250.38 96.127.250.34 96.127.250.30 96.127.250.29 96.127.250.27 96.127.250.23 96.127.250.19 96.127.250.15 96.127.250.59 96.127.250.57 96.127.250.53 96.127.250.49 96.127.250.45 2607:f8b0:4006:80f::200e Connecting to 96.127.250.44 Nav_open_url: new url='http://images.google.com/search?q=bra&tbm=isch' Connecting to 96.127.250.44 >>>> a_Nav_repush <<<< Nav_open_url: new url='http://images.google.com/search?q=bra&tbm=isch' a_Nav_expect_done: repush! Nav_open_url: new url='http://images.google.com/search?q=bra&ie=UTF-8&tbm=isch&gbv=1&sei=zkNNVd6sI…' Connecting to 96.127.250.44 >>>> a_Nav_repush <<<< Nav_open_url: new url='http://images.google.com/search?q=bra&ie=UTF-8&tbm=isch&gbv=1&sei=zkNNVd6sI…' a_Nav_expect_done: repush! Nav_open_url: new url='http://images.google.com/search?q=bra&ie=UTF-8&tbm=isch&gbv=1&sei=zkNNVYTpK…' Connecting to 96.127.250.44 >>>> a_Nav_repush <<<< ... and so on, extermely quickly, which then results in Google temporarily blocking me since Dillo is behaving like a DDOS attacker :s. Any idea what's causing these repush'es? I'm pretty sure nothing changed on my end. Other browsers work for me (eg. Links, Uzbl). Changing the User Agent had no effect.

4 9

Patch: fix the flowchart diagram in the dw::Table class docs
by onepoint＠starurchin.org 02 Jun '15

02 Jun '15

The main body of the dw::Table class documentation starts with a flowchart diagram of some dw::Table method calls. But this diagram refers to a method dw::Table::calcColumnExtremes() that is no longer used and has been renamed to dw::Table::_unused_calcColumnExtremes(). (There is a warning that GROWS made some of this documentation obsolete.) So I dug into the code and came up with a patch that I think fixes the diagram. I have attached before and after images of the diagram so that you can compare. I would love some feedback! http://starurchin.org/dillo/patch/doxygen-dw-table-hh-dependency-diagram.ht… And this patch removes dw::Table::_unused_calcColumnExtremes(). http://starurchin.org/dillo/patch/remove-dw-table-_unused_calcColumnExtreme… Comments are welcome. Regards, Jeremy Henty

2 1

Documentation in the tarball?
by sgeerken＠dillo.org 01 Jun '15

01 Jun '15

Hi! Does it make sense to include all developer documentation into the tarball? As an alternative, only user documentation, plus a notice where to find the developer docs, could be included, while the rest can only be found in the repository at hg.dillo.org. I assume that someone who is interested in the internals of dillo will anyway refer to the lastest version from the Hg repository. Keeping it out of the tarball would have advantages: - It makes the tarball smaller. - We developers would not have to think that much about file sizes of the documentation: these files do not go into the tarball; and for those using the lastest version from the Hg repository, it should be reasonable to spend some more disc space. What do you think? Sebastian

3 4

Oh, list moderator...
by onepoint＠starurchin.org 01 Jun '15

01 Jun '15

(I hope you will take this in the light-hearted tone that I wrote it. I don't often write poetry.) Oh, list moderator, help me please. I sent the list an email with attached PNGs. I saw there was a problem, had an itch to scratch. And that's why I was hoping you would take my patch. But I knew that you would need some actual evidence To show you what I'm saying really makes some sense. I saw a flowchart image in the HTML page And noticed with regret that it had rotted with age. It linked to a method that wasn't there no more And that's when I decided I should settle this score. I made a better version and then sent it to you And I chose to enclose the original too But sadly those two images were too big for the list So now now your mailer's told me I should cease and desist. Please, list moderator, let my work through. Whatever you may think I only did it for you. I have helped you before, I want to help you once more. But you've got to tell your mail software to open the door. Regards, Jeremy Henty

3 2