- Dillo-dev - lists.mailman3.com

experimental patch: image error status as alt text
by corvid＠lavabit.com Dec. 28, 2008

Dec. 28, 2008

You know how for image redirections and 404s, nothing at all happens? User's mind: "I didn't get the image. Dillo must be broken." (or the address can't resolve, or content-type doesn't match...) So I tried making something recently that shows, e.g., [404] as the alt text. In this form it's probably wrong in a design sense because cache probably isn't allowed to call image, but maybe it'll prompt some discussion... (and maybe it'd be better to pull the status out of the header whenever needed rather than adding more junk to the cache entry.)

2 2

gmail access
by furaisanjin＠gmail.com Dec. 23, 2008

Dec. 23, 2008

Hi all. Now I figure out the way to access gmail but I realize that isn't sophisticated. Anyway what I have modified dillo after all is add "force reload link" feature. This is the step to access gmail 1. Goto gmail.com and login in. 2. You will see meta redirect page so just force reload the link on meta redirect link. However you won't go anywhere yet. 3. Goto mail.google.com/mail, then you find link to simple HTML page. If some of you are interested the patch, I will post. Regards, furaisanjin

1 1

Re: Dillo-dev Digest, Vol 40, Issue 22
by daniel.victoria＠gmail.com Dec. 23, 2008

Dec. 23, 2008

Regarding Gmail access... I'm certanly interested in a patch Thanks Daniel On Tue, Dec 23, 2008 at 9:00 AM, <dillo-dev-request(a)dillo.org> wrote: > Send Dillo-dev mailing list submissions to > dillo-dev(a)dillo.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > or, via email, send a message with subject or body 'help' to > dillo-dev-request(a)dillo.org > > You can reach the person managing the list at > dillo-dev-owner(a)dillo.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Dillo-dev digest..." > > > Today's Topics: > > 1. gmail access (furaisanjin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 23 Dec 2008 09:28:14 +0900 > From: furaisanjin <furaisanjin(a)gmail.com> > Subject: [Dillo-dev] gmail access > To: Dillo-dev(a)dillo.org > Message-ID: > <144aa14b0812221628v71c176b2vf504b5bfe663e5b9(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all. > > Now I figure out the way to access gmail but I realize that isn't sophisticated. > > Anyway what I have modified dillo after all is add "force reload link" feature. > > This is the step to access gmail > 1. Goto gmail.com and login in. > 2. You will see meta redirect page so just force reload the link on > meta redirect link. However you won't go anywhere yet. > 3. Goto mail.google.com/mail, then you find link to simple HTML page. > > If some of you are interested the patch, I will post. > > Regards, > furaisanjin > > > > ------------------------------ > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > > End of Dillo-dev Digest, Vol 40, Issue 22 > ***************************************** >

1 0

a little ad blocker
by corvid＠lavabit.com Dec. 22, 2008

Dec. 22, 2008

If you would like one just to play with, well then: http://www.dillo.org/test/adblocker.patch (Blocking * pretty much suffices for me, so I might as well put it there as-is before I become dangerously bored with it.)

1 0

HTTP/1.1 side effect
by jcid＠dillo.org Dec. 21, 2008

Dec. 21, 2008

Hi, @corvid: while debugging the CSS loading patch, I noticed that sometimes dillo doesn't get the close after transfer event. This is needed to trigger the CSS parser with a full sheet. For instance, go to http://localhost:631/ (CUPS interface), and the progress bar will not get inactive after the page is got. Now, if you switch http.c to HTTP/1.0 queries, it will work as expected. Is there something missing, or a way to hook this? -- Cheers Jorge.-

2 1

[patch]: Basic Authentication
by onepoint＠starurchin.org Dec. 21, 2008

Dec. 21, 2008

OK, here it is. Please comment. Some observations: When the cache parses the HTTP header we just attach any authentication headers to the cache entry. Nothing else happens until we process the clients. Just before iterating over the clients we check if all the data is in. If it is then we do any necessary authentication. Opening the authentication dialog runs the FLTK event loop, which means that incoming data can call the cache again, triggering CCC warnings. We work around it by deferring the dialog to a timeout so that the cache finishes iterating over the clients before the dialog appears. This is annoying but I don't see a better way at the moment. The authentication dialog does not know which browser window opened the URL so it can't call a_Nav_reload(). Instead I implemented a_Nav_reload_url(). There's an interesting case when the server demands authentication for a realm that we have already authenticated ourselves to. It could be that we didn't send authentication because we didn't know the path was in the realm, or it could be that the authentication we sent was wrong. This requires the code to deduce what it did last time it saw this URL and rely on what it will do the next time. It works, but it feels fragile to me. I would prefer the URL to explicitly record authentication attempts so that the code doesn't have to second-guess itself. Thoughts? I implemented a full token-value list parser as per the RFC. Maybe this is overkill for Basic authentication, but it will be necessary for Digest authentication. Yes, it has gotos; I began by setting flags but decided that gotos were actually cleaner. Maybe it should be rewritten in state-machine style? If the user opens several pages in a realm in a very short time then it is conceivable that multiple authentication dialogs for the same realm could pop up (just like the https DPI sometimes does with certificate dialogs). I don't address this at the moment because I think it won't be a problem in practice. If it needs fixing then we will have to monitor the list of currently open dialogs to avoid duplicates. Regards, Jeremy Henty

4 8

[patch]: Basic Authentication
by onepoint＠starurchin.org Dec. 21, 2008

Dec. 21, 2008

Next iteration: one bugfix. * In Auth_parse_auth_basic(), fix the test for the "realm" token. Jeremy Henty

3 3

patch: error pages from file dpi
by corvid＠lavabit.com Dec. 21, 2008

Dec. 21, 2008

What do you think of sending little HTTP error pages for file not found and so on? I always find it a little jarring when nothing happens and I have to look down at the status bar for the error.

3 2

Mercurial repository
by jcid＠dillo.org Dec. 21, 2008

Dec. 21, 2008

Hi, The source code repository page was updated to Mercurial. Please send me the patches as advised there, and please add a one-liner entry in the ChangeLog file. That way it'kll be easier for me and proper credits will appear in both. -- Cheers Jorge.-

1 0

Re: CSS loading, part 1
by Johannes.Hofmann＠gmx.de Dec. 19, 2008

Dec. 19, 2008

Hi Jorge, On Fri, Dec 19, 2008 at 03:37:28PM -0300, Jorge Arellano Cid wrote: > Hi Johannes, > > The attached patch does better than the current way, it has > more consistency betweeen what's shown the first time and after > back and forward (at least with my test set). > > Please test it and apply to the css-proto tree. Thanks! Pushed to css-prototpe. > > I don't know what's to be done when multiple stylesheets are > specified, like in this site: http://www.lacuarta.cl. Are they > all supposed to be loaded? If that's the case, I'd like to load > them all and after that, make a single repush instead of one per > arrival. Yes, all stylesheets with a matching media type have to be loaded. I noticed a regression on http://src.opensolaris.org/source/ Maybe it's because now only one stylesheet is loaded? I agree that having just a single repush is probabely better. I don't yet fully understand the new logic and the difference to corvid's approach. Are the style changes in css.cc and css.hh intentional? Generally it would be good to keep whitespace only changes in separate commits. That simplifies reviewing and the search for faulty changesets. BTW. "hg bisect" is a fanatastic tool for that! (similar stuff exists for git too of course). > > If that scheme is implemented, then it'd be simple to extend > the code to parse this case: > > <style type="text/css" media="all"> > @import url('/style.css'); > </style> > > > BTW, it's a very nice feeling to see CSS working. Yes it's fun! Cheers, Johannes

2 1