- Dillo-dev - lists.mailman3.com

client-side redirect
by corvid＠lavabit.com July 5, 2009

July 5, 2009

I went to http://home.williampoundstone.net/Keeler/ and it breaks because there's a space before the URL in <meta http-equiv="refresh" content="0;url= Home.html" /> I can't seem to find anything that does a careful job of specifying what's legal here.

1 0

dillo-2.1.1 released
by corvid＠lavabit.com July 5, 2009

July 5, 2009

The purpose of this release is to prevent a maliciously-crafted image from causing an overflow. Since this is a matter of security, everyone is, naturally enough, encouraged to upgrade :) Thanks go to the oCERT folks for bringing the matter to our attention. (Jorge will send the freshmeat announcement in a little bit, and I will finish updating the website in a moment...)

4 4

dillo 2.1]
by sandshrew＠gmail.com July 4, 2009

July 4, 2009

Accidentally sent to corvid only. Forwarding to dillo-dev. > > > It seems whoever designed the new website theme has no idea what > > > READABILITY means... It looks like someone just used some stupid online > > > color picker, which just picks some similar colors to the one user > > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > > regression... > > > > Hm I like the new design, but I agree that readability might be a problem. > > Let's see what other say. > > I still find visited text to be hard to read, but I know I should > break down and get a new display... > I wonder if you are the only dillo user with old display... BTW, I am using pretty new LCD display and still find it hard to read.

4 7

Tango icon theme for Dillo 2.1.1
by xentalion＠gmail.com July 4, 2009

July 4, 2009

Skipped content of type multipart/alternative

2 2

dillo 2.1.1
by corvid＠lavabit.com July 3, 2009

July 3, 2009

We're planning a bugfix release because it turns out that the PNG image size fix added right before the 2.1 release was incorrect. The nominal release date is Friday, but of course we'll see... Considering how I ripped out a bunch of extraneous system includes right after the 2.1 release, it would be a comfort to know that the code in the repository still compiles for everyone.

5 6

Re: Feels good to be free. Close-tab button.
by jorl17.8＠gmail.com July 2, 2009

July 2, 2009

Ter, 2009-06-30 ?s 22:43 +0100, Jo?o Ricardo Louren?o escreveu: > Well, I promised I would report to you when I got more free time. > Guess what, I'm on vacation! Getting free time from my own personal > projects finally lets me take a closer look at Dillo. I am sorry for > being away for such a long time, though. > > I would like to contribute to one area that I have contributed > previously -- the close-tab button. It isn't critical, I know, but, > for now, it's the best I can do. The idea now is to finally have a > button in each tab. > > It is tough, but I am getting somewhere. The 'initial' drawing part is > done, but I have had to make some small changes to some virtual > functions, and also changing non-virtual functions and finding a way > to 'enable' them in the code. > > It's pretty hackish right now, but I have managed to print the button > and am now starting to handle all the events and different button > states (clicked, over, etcetera). > > I'll keep you updated! > > Jo?o Answering myself, I've got the system working! There are still many more code-cleanups to do and add a couple of documentation features here and there.... It isn't 'pretty', but someone with more skills in the 'design' area can do better than me, I've got the system (which is pretty dumb and slow, IMO). There are, however, three issues I have: 1. I still haven't sorted things with the pager to have tabs behave 'correctly', but that should be _too_ hard, just quite some research. 2. When I destroy a tab, their order gets 'mixed up', but only sometimes. 3. For some reason, clicking on some tabs isn't working (not the buttons, but the tabs). I'll go into them and I think that 3 and 2 are related. I just decided to inform all of you how progress was going. Jo?o

4 9

Feels good to be free. Close-tab button.
by jorl17.8＠gmail.com June 30, 2009

June 30, 2009

Well, I promised I would report to you when I got more free time. Guess what, I'm on vacation! Getting free time from my own personal projects finally lets me take a closer look at Dillo. I am sorry for being away for such a long time, though. I would like to contribute to one area that I have contributed previously -- the close-tab button. It isn't critical, I know, but, for now, it's the best I can do. The idea now is to finally have a button in each tab. It is tough, but I am getting somewhere. The 'initial' drawing part is done, but I have had to make some small changes to some virtual functions, and also changing non-virtual functions and finding a way to 'enable' them in the code. It's pretty hackish right now, but I have managed to print the button and am now starting to handle all the events and different button states (clicked, over, etcetera). I'll keep you updated! Jo?o

1 0

[PATCH] warning: ignoring return value of ‘int chdir(const char*)’
by newman.x＠gmail.com June 27, 2009

June 27, 2009

gcc-4.4.0-4.i586 HG tip: newman src $ make | grep -i warning [...] paths.cc: In static member function ?static void Paths::init()?: paths.cc:38: warning: ignoring return value of ?int chdir(const char*)?, declared with attribute warn_unused_result With the patch dillo-guard-chdir.patch no warning. But this patch alone won't have any effect, all MSG(...) from Paths::init() won't write anything to output due to prefs.show_msg not being set to TRUE at that moment. Patch dillo-use-MSG-asap.patch moves a_Prefs_init() before Paths::init() is called. Hope it's not breaking anything. Tested - setting non-existing directory instead of /tmp - Dillo won't crash on start, basic browsing works -- Regards, Michal Nowak

3 4

[marcio.ccamargo@gmail.com: Thank u!]
by jcid＠dillo.org June 25, 2009

June 25, 2009

Hi, :) -- Cheers Jorge.-

1 0

patch: save bookmark segfault when dpis not found
by corvid＠lavabit.com June 24, 2009

June 24, 2009

A new one seen in the bugtracker... a_Bookmarks_chat_add() sets URL to NULL, so it needs to be handled. Anyway, the reason this is interesting is that I had always figured the URL_*() macros were protecting against a NULL URL, when really they protect against NULL fields in URLs.

2 2