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@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@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
Globe Trotter ha scritto:
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.
Absolutely interesting! :-) With all, (except those are for profiling) options active: 448k size 420k du -k It did not compile with --disable-cookies IMHO becau se line 687 in src/cache.c "#ifndef DISABLE_COOKIES" should move in 652 I think line 3838 and 3819 in src/html.c should have 1 (the lesser integer bigger than 0) as minimum reload time instead of 7 (which is an arbitrary choosen value). official dillo with default configure 378k size 348k du -k So they differ for 70kb which are 20% of dillo, not so little, not so much. Home users should not care about 70kb more or less, embedded developers could/would but probably they have the skills to reduce dillo down its minimal size (or apply patch -R in order to reduce size). However... I think Jorge (the author of dillo) should have to, at least, link this patch-groups on dillo webpage in order to avoid people to waste their time rewriting the same functionalities (people who probably are contributing to others gpl projects, so wasting their time means wasting free developing community resources). I do not blame him for his choose to left this patches out in the cold but there are no any reasons because people could not be awarned that exists an unofficial dillo patches reposity. If Jorge is quite sure about his choose (stay close to minimum size/features) should not have any fear that unofficial patches hurts dillo, doesn't he? ;-) Cheers, -- Roberto A. Foglietta Analista Programmatore GNU/Linux SAD Trasporto Locale S.p.a. Corso Italia 13/N 39100 BOLZANO (I) Tel. +39/0471-450.261 Fax +39/0471-450.253
participants (2)
-
Globe Trotter -
Roberto A. Foglietta