- Dillo-dev - lists.mailman3.com

Fixing bug in parsing HTML 4.01 comments
by Michal Nowak Jan. 22, 2006

Jan. 22, 2006

Hi developers there, I found (hope so) a bug in parsing HTML comments. Acording to HTML 4.01 spec it is possible to make such a comment: " tag. */ while ( (p = memchr(buf + buf_index, '>', bufsize - buf_index)) ){ buf_index = p - buf + 1; - if ( p[-1] == '-' && p[-2] == '-' ) break; + gint counter = -1; + while (isspace(p[counter])) + counter--; + if ( p[counter] == '-' && p[counter-1] == '-' ) break; } if ( p ) { /* Got the whole comment. Let's throw it away! :) */ It's hackish and ugly. I know. From: http://www.w3.org/TR/html4/intro/sgmltut.html#h-3.2.4 "White space is not permitted between the markup declaration open delimiter("<!") and the comment open delimiter ("--"), but is permitted between the comment close delimiter ("--") and the markup declaration close delimiter (">"). A common error is to include a string of hyphens ("---") within a comment. Authors should avoid putting two or more adjacent hyphens inside comments." Michal Nowak

4 4

xhtml1.1 DOCTYPE
by Michal Nowak Jan. 21, 2006

Jan. 21, 2006

Hi everyone, hola Jorge, I tried the new CVS version of dillo with the DOCTYPE patch from Jorge. It works good with HTMP 4.01 and XHTML 1.0 but do not recognize XHTML 1.1. Here's the output: Nav_open_url: Url=>http://www.stud.fit.vutbr.cz/~xnowak01/tea-service/index.html< Connecting to 147.229.10.14 Doctype: 0.000000 New: {<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">} Doctype: 0.000000 Doctype: 0.000000 -- # Michal Nowak <newman [DOT] x [AT] seznam [DOT] cz> # jabber: nowak[AT]jabber.cz # irc: channel #wmii [AT] irc.oftc.net as newman # icq: 170814295

2 2

BUG#655
by Jorge Arellano Cid Jan. 21, 2006

Jan. 21, 2006

Hi Matthias, I just commited a patch for BUG#655 (escaping of SGML reserved characters in bookmarks dpi). Please give it a try. I made some tests but not in much depth. Ah, there's also a fix for 'dpidc' (now it should work again! :-) -- Cheers Jorge.-

1 0

Re: [Dillo-dev] Dillo 0.8.5 with gmail
by Globe Trotter Jan. 20, 2006

Jan. 20, 2006

Hi, I don't believe that dillo supports javascript and ever will. The author seems to believe that a browser should be as stripped down and non-functional as possible or as bloated as possible (such as mozilla or firefox), with nothing in between. I would like that something in between. I think a lot of us on this mailing list (me at least) would be very appreciative if you could make support for it. You may consider teaming up with http://teki.jpn.ph/pc/software/index-e.shtml which provides unofficial versions of dillo with additions. Be forewarned that dillo is going to change to fltk so you may want to wait for that to happen first. There is no point in wasting time and creating something that will go away. Apparently, two copies with fltk exist, but have never been released. They are supposed to be released in the next version. Many thanks and best wishes! > > --- Richard <judicator3(a)gmail.com> wrote: > > > Hello, > > > > I have compiled and installed Dillo 0.8.5 and enabled the https DPI. I am > > trying to use Dillo to log in to gmail. I have made sure that cookies are > > enabled for .gmail.com. I am able to get the gmail login page which is > > served through https but I cannot log in to my account. > > > > After clicking on the "Sign In" button and accepting all the certificate > > warnings messages, I am not redirected to my mailbox and I am stuck on the > > gmail login page. Does dillo support javascript ? and is that the reason > why > > I cannot login to gmail ? If javascript is the stopper that prevents dillo > > from being used on gmail, hotmail or yahoo etc... then I am willing to > > devote some time to get something like SpiderMonkey or some other JS engine > > to work with Dillo. > > > > I was running dillo from the command line and below is the output I got > from > > the console. Notice that dillo seems to die in the https.filter.dpi. I have > > looked at the mailing archives and I think I saw other people being able to > > at least login to gmail. So I am not sure what is going on in my case. Is > > there a later unstable version of Dillo I should use in order to login to > > gmail ? > > ============================================================== > > Dpi_parse_token: [<dpi cmd='dialog' msg='The remote certificate cannot be > > verified20' alt1='Continue' alt2='Cancel'>] > > a_Dpiapi_dialog: > > dpip_tag: <dpi cmd='dialog' msg='The remote certificate cannot be > > verified20' alt1='Continue' alt2='Cancel'> > > Dpi_parse_token: [<dpi cmd='start_send_page' url=' > > https://mail.google.com/mail/images/corner_tl.gif'>] > > { exiting https.dpi} > > Dpi: [Dpi_process_io] IOClose > > Nav_open_url: Url=>https://www.google.com/accounts/ServiceLoginAuth< > > main.c:154: get_command: dpid tag is NULL > > : main.c:328: main: get_command failed > > : {In https.filter.dpi} > > Dpi_parse_token: [<dpi cmd='dialog' msg='The remote certificate cannot be > > verified20' alt1='Continue' alt2='Cancel'>] > > a_Dpiapi_dialog: > > dpip_tag: <dpi cmd='dialog' msg='The remote certificate cannot be > > verified20' alt1='Continue' alt2='Cancel'> > > { exiting https.dpi} > > Dpi_parse_token: [<dpi cmd='start_send_page' url=' > > https://mail.google.com/mail/images/corner_tr.gif'>] > > Dpi: [Dpi_process_io] IOClose > > ============================================================== > > > > Thanks > > Best regards > > Richard Ta-Min > > > _______________________________________________ > > Dillo-dev mailing list > > Dillo-dev(a)dillo.org > > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

downloads.dpi feedback
by Michal Nowak Jan. 19, 2006

Jan. 19, 2006

Hi there, here are some of my thoughts of new FLTK downloads.dpi iterface: 1. Because I use the wmii (www.wmii.de) - it's tabbed wm, like ratpoison and unlike KDE - I am very glad when no extra windows pops up from some app. For me it would be nice if the download manager opens in some dillo's tab window and not separate. 2. There are some curves on right and bottom side, they look ugly and useles. There should be some decent separator between two downloads. I don't like the shadow under the "file" field. It will be nice if the progres bar will be rightmost. 3. When the download is finished, on the button is 'done' text. It's nice to know that the download is done but when I click it cleans it, so we should rename 'done' -> 'clean'. 4. Buttons: Abort: stop and delete unfinished file Pause/Resume: SIGTERM (or SIGSTOP) wget/(SIGCONT) wget -c %f But I guess well polished download manager isn't necessary now, it's useful only for normal users. Regards -- # Michal Nowak <newman [DOT] x [AT] seznam [DOT] cz> # jabber: nowak[AT]jabber.cz # irc: channel #wmii [AT] irc.oftc.net as newman # icq: 170814295

1 0

Re: [Dillo-dev] Dillo 0.8.5 with gmail
by Richard Jan. 15, 2006

Jan. 15, 2006

Hello Thanks for the quick response. Most probably. Disable javascript in Firefox and try to log in. > That's a good starting point. Yes I tried that with firefox and JS disabled. Gmail is smart enough to send you a version of the HTML page that does not require JS and you can log in. So JS is probably not the issue why I cannot login with dillo. I had some more time yesterday to look into the problem. It seems for whatever reason, dillo is not sending the form's POST HTTP request when I click on the "Sign In" button of the login form. I'll look into the problem. If it is truly a bug I'll let you guys know. Good. Is JS your expertise area? Not exactly. I am working of some other project right now, but later I may have the necessary time to devote in learning. I'll keep the JS issue in the back of my mind. Best regards Richard Ta-Min

3 4

Current color control??
by Beartooth Jan. 14, 2006

Jan. 14, 2006

I had my newsreader search 'color', but all I found was an exchange from 2003, and I doubt that's current. I have Dillo set as my default browser (under Fedora Core 4); every once in a while I get some site that's unreadable, because the text and background are too near the same color. My next move is to try the same URL in another browser; and that usually solves it. Can I make Dillo do whatever it is that the others do to remedy this, or not do whatever it does if it's creating it? -- Beartooth Stickster, Neo-Redneck Linux Enthusiast A wanderstaff like an Elvish rope should be long, and strong, and light -- and very smooth.

2 2

[jcid@dillo.org: Re: [Dillo-dev] Dillo 0.8.5 with gmail]
by Jorge Arellano Cid Jan. 13, 2006

Jan. 13, 2006

-- Cheers Jorge.-

1 0

Dillo 0.8.5 with gmail
by Richard Jan. 13, 2006

Jan. 13, 2006

Hello, I have compiled and installed Dillo 0.8.5 and enabled the https DPI. I am trying to use Dillo to log in to gmail. I have made sure that cookies are enabled for .gmail.com. I am able to get the gmail login page which is served through https but I cannot log in to my account. After clicking on the "Sign In" button and accepting all the certificate warnings messages, I am not redirected to my mailbox and I am stuck on the gmail login page. Does dillo support javascript ? and is that the reason why I cannot login to gmail ? If javascript is the stopper that prevents dillo from being used on gmail, hotmail or yahoo etc... then I am willing to devote some time to get something like SpiderMonkey or some other JS engine to work with Dillo. I was running dillo from the command line and below is the output I got from the console. Notice that dillo seems to die in the https.filter.dpi. I have looked at the mailing archives and I think I saw other people being able to at least login to gmail. So I am not sure what is going on in my case. Is there a later unstable version of Dillo I should use in order to login to gmail ? ============================================================== Dpi_parse_token: [<dpi cmd='dialog' msg='The remote certificate cannot be verified20' alt1='Continue' alt2='Cancel'>] a_Dpiapi_dialog: dpip_tag: <dpi cmd='dialog' msg='The remote certificate cannot be verified20' alt1='Continue' alt2='Cancel'> Dpi_parse_token: [<dpi cmd='start_send_page' url=' https://mail.google.com/mail/images/corner_tl.gif'>] { exiting https.dpi} Dpi: [Dpi_process_io] IOClose Nav_open_url: Url=>https://www.google.com/accounts/ServiceLoginAuth< main.c:154: get_command: dpid tag is NULL : main.c:328: main: get_command failed : {In https.filter.dpi} Dpi_parse_token: [<dpi cmd='dialog' msg='The remote certificate cannot be verified20' alt1='Continue' alt2='Cancel'>] a_Dpiapi_dialog: dpip_tag: <dpi cmd='dialog' msg='The remote certificate cannot be verified20' alt1='Continue' alt2='Cancel'> { exiting https.dpi} Dpi_parse_token: [<dpi cmd='start_send_page' url=' https://mail.google.com/mail/images/corner_tr.gif'>] Dpi: [Dpi_process_io] IOClose ============================================================== Thanks Best regards Richard Ta-Min

1 0

Re: [Dillo-dev] Re: patch: python filter DPI supporting the "data:" scheme from RFC 2397
by Jorge Arellano Cid Jan. 5, 2006

Jan. 5, 2006

Hi Ben, On Fri, Dec 30, 2005 at 03:18:12PM -0800, Ben Wiley Sittler wrote: > yes!let me know when the c translation is uploaded and i will gladly > take a look. i have investigated the mp3 thing further, and basically > dillo is not well-prepared to deal with very long uris, especially not > ones handled by a dpi. probably a maximum should be chosen (max. pipe > buffer size less the size of the overhead bytes for the rest of the > dpi request, maybe?) and anything longer should generate an error > message inside dillo. The patch took some time because it uncovered a subtle parsing bug in Dpip. It's fixed now in CVS. Both the new datauri.c and the dpip fix were commited. This is a no-frills datauri dpi version. There're things to polish. For instance: URI="data:;,test" // empty base64 and media type, ";" should be ignored > > separately, much of the dillo core is unprepared to handle data: URIs; > for instance, it tried to generate filenames when saving that are > longer than the OS and filesystem maximum length, and also slow down > the GUI to unusable speeds due to font metric calculations. > furthermore it did not use the mime-types database to select a > filename extension, so they ended up with very cryptic names. Yes, this can also be improved. > as for the python dpi, maybe keep it as an example in the source tree > but don't install it when doing 'make install', and use the new C > implementation as the default? maybe some python programmer will take > it and turn it into something more useful... It didn't work for me so currently it's not in CVS. > also, do the dpi-handling functions in the python dpi seem correct, or > did i misunderstand the protocol? i was not so sure about the > quoting/escaping mechanisms... This was a bit fuzzy... I changed it a bit and commented much more in dpip/dpip.c. Data URIs are a bit delicate with regard to security. This also needs some work. Although datauri is enabled now, it may be disabled for the next release unless security is stronger. -- Cheers Jorge.-

1 0