December 2008 - Dillo-dev - lists.mailman3.com

remove generate_submit pref?

by onepoint＠starurchin.org

On Fri, Dec 26, 2008 at 02:44:52AM +0000, corvid wrote: > Any objections to getting rid of it? No. IIRC that was a code path that got in the way of refactoring form.cc when I last looked at it, so I wouldn't be surprised if the code was improved by losing it. Regards, Jeremy Henty

Dec. 26, 2008

remove generate_submit pref?

by corvid＠lavabit.com

Any objections to getting rid of it? dillorc: # Some forms lack a submit button, and dillo can generate a custom one # internally. Unfortunately there's no guarantee for it to work. :( # (my experience is that forms that lack a submit rely on Javascript) #generate_submit=NO

Dec. 26, 2008

Re: CSS loading part#2

by jcid＠dillo.org

Hi, On Sun, Dec 21, 2008 at 04:48:42PM -0300, Jorge Arellano Cid wrote: > Hi Johannes, > > Here I'm attaching the second part of the CSS loading patch. > This one is coherent and works better :-). Please commit after > some testing. > > Note: images are still truncated sometimes, but AFAIS this is a > problem in the dicache, not in CSS loading. I hope to fix this > soon. Well, in fact, images were always truncated when the repush caught them still rendering. I've been working on this for days and yes, it's a problem in the dicache. Unfortunately the cache/dicache/image-decode/image code is so entangled that it needs a rewrite. Quite surprising it works stable "as is". The idea is to try to devise a single path of execution that allows handling each image request (repeated or not) as a simple cache client. It's more complex than it sounds! The good news is that after you merge the latest cleanups in dillo main, the attached patch will more or less make it work as desired. There'll be some added unstability, and the underlying mess ;), but it should be a good basis to keep improving CSS while I work in the image process stream. -- Cheers Jorge.- _... o_.-"` `\ .--. _ `'-._.-'""-; _ .' \`_\_ {_.-a"a-} _ / \ _/ .-' '. {c-._o_.){\|` | (@`-._ / \{ ^ } \\ _/ `~\ '-._ /'. } \} .-. |>:< '-.__/ '._,} \_/ / ()) | >:< `'---. ____'-.|(`"` \ >:< \\_\\_\ | ; \ \\-{}-\/ \ \ '._\\' /) '. /( `-._ _____ _ _____ __.'\ \ / \ / \ / \ \ \ jgs _.'/^\'._.'/^\'._.'/^\'.__) \ ,==' `---` '---' '---' ) `"""""""""""""""""""""""""""""""`

Dec. 25, 2008

Re: gmail access

by furaisanjin＠gmail.com

The patch is attached in this e-mail. Regards, furaisanjin

Dec. 23, 2008

Re: Dillo-dev Digest, Vol 40, Issue 22

by daniel.victoria＠gmail.com

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 > ***************************************** >

Dec. 23, 2008

gmail access

by furaisanjin＠gmail.com

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

Dec. 23, 2008

experimental patch: image error status as alt text

by corvid＠lavabit.com

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.)

Dec. 22, 2008

a little ad blocker

by corvid＠lavabit.com

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.)

Dec. 22, 2008

HTTP/1.1 side effect

by corvid＠lavabit.com

Jorge wrote: > @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? Searching for "cups" and "Connection: close", I found http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504727 which says: | The client uses HTTP 1.1 and includes the |"Connection: close" header meaning that he wants that request to |be the last one. cups replies with a "Connection: keep-alive" |header and doesn't close its end of the connection, which is in |violation of the HTTP 1.1 RFC.

Dec. 21, 2008

HTTP/1.1 side effect

by jcid＠dillo.org

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.-

Dec. 21, 2008