June 2012 - Dillo-dev - lists.mailman3.com

dillo.org web site

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > Things seems to be working since yesternight. > @all: Please confirm. It all looks good from here. dnsip reports 134.102.206.165 as the only IP for both dillo.org and www.dillo.org . Dillo, links and Firefox all redirect from dillo.org to www.dillo.org . Regards, Jeremy Henty

June 7, 2012

dillo.org web site

by rogerx.oss＠gmail.com

> On Thu, Jun 07, 2012 at 10:43:03AM -0400, Jorge Arellano Cid wrote: >Hi, > > Things seems to be working since yesternight. > @all: Please confirm. ... dang I'm good! -- Roger http://rogerx.freeshell.org/

June 7, 2012

dillo.org web site

by sgeerken＠dillo.org

On Thu, Jun 07, Jorge Arellano Cid wrote: > Things seems to be working since yesternight. > @all: Please confirm. Looks good: --- sg at sg4:~$ nslookup dillo.org Server: 192.168.178.1 Address: 192.168.178.1#53 Non-authoritative answer: Name: dillo.org Address: 134.102.206.165 sg at sg4:~$ nslookup www.dillo.org Server: 192.168.178.1 Address: 192.168.178.1#53 Non-authoritative answer: Name: www.dillo.org Address: 134.102.206.165 -- Also, I don't see any other problems. Sebastian

June 7, 2012

[patch] HTML parser bugfix

by p37sitdu＠lavabit.com

Forgot to attach.

June 7, 2012

dillo.org web site

by jcid＠dillo.org

Hi, Things seems to be working since yesternight. @all: Please confirm. -- Cheers Jorge.-

June 7, 2012

dillo.org web site

by higuita7＠yahoo.co.uk

Hi > Another way to solve the problem may be to point to a working > nameserver elsewhere too (the API seems to allow this option). > I'll ask Andreas K. whether we can point to the wearlab DNS in > the interim. If needed, i recommend the https://dns.he.net/ as a very good free dns hosting, i use it myself higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946

June 7, 2012

[patch] HTML parser bugfix

by p37sitdu＠lavabit.com

On Thu, Jun 07, 2012 at 12:14:06AM +0100, Jeremy Henty wrote: > > 123 wrote: > > > On Sun, Jun 03, 2012 at 09:00:55PM +0100, Jeremy Henty wrote: > > > > If you don't detect and ignore that extra double quote you will > > > break many pages that every other browser renders perfectly well. > > > > Then there should be some logic for detecting double quotes. > > I agree. The hard question is: what logic? IMO the right way to do it is to implement HTML Standard [1]. When Html_write_raw is called, parser is in the Data state. When it returns to Data state again, it is the end of token. I have implemented standard comment/DOCTYPE parsing. It is incomplete, EOF is not handled and DOCTYPE parsing is not changed. Patch is attached. Next step is to rewrite tag parsing in standard way. [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.ht…

June 7, 2012

[patch] HTML parser bugfix

by onepoint＠starurchin.org

123 wrote: > On Sun, Jun 03, 2012 at 09:00:55PM +0100, Jeremy Henty wrote: > > If you don't detect and ignore that extra double quote you will > > break many pages that every other browser renders perfectly well. > > Then there should be some logic for detecting double quotes. I agree. The hard question is: what logic? > Searching for < inside quotes is not the right way as it breaks > valid pages like reddit main page. Again, I agree. In fact, I decided to experiment with removing Dillo's misquote-detection just because it broke reddit. Unfortunately it is very hard to come up with an algorithm that correctly handles the various quoting horrors that you see all the time, yet also correctly parses embedded javascript fragments like: onclick='alert("clicked")' (IIRC Dillo mis-renders reddit because of embedded javascript like this.) > Can you give examples of real web pages with double quotes? I have attached a bunch of links that I collected after spending a lot of time debugging pages that broke my locally-patched Dillo. (Ignore the file:///... URLs as they obviously won't work for you.) I have also attached the two patches I use. I think the first does the same thing that you propose, although I haven't checked that in detail. The second attempts to copy Firefox's misquote-detection algorithm. I agree that Dillo's misquote-detection isn't good enough, but just taking it out is a step backwards, and it is a mistake to propose changes to it based solely on particular pages that Dillo mis-renders, because any such change needs to be tested against the many other broken pages that Dillo currently renders more or less correctly. Regards, Jeremy Henty

June 6, 2012

dillo.org web site

by jcid＠dillo.org

[here goes the attachement] -- Cheers Jorge.-

June 6, 2012

dillo.org web site

by jcid＠dillo.org

On Tue, Jun 05, 2012 at 02:52:08PM -0800, Roger wrote: > > On Tue, Jun 05, 2012 at 02:03:12PM -0400, Jorge Arellano Cid wrote: > >On Tue, Jun 05, 2012 at 11:28:40AM +0100, Jeremy Henty wrote: > >> > >> Jorge Arellano Cid wrote: > >> > >> > The domain was renewed, but I still can't see the website from > >> > Chile, although when I log to the wearlab it works [1]. > >> > >> Using dillo, Firefox and links, www.dillo.org works but dillo.org > >> returns nothing but some <script> elements from sedoparking.com . > > > > It doesn't work here... :( > > > > Yesterday I filled a "Case management" ticket at dotster > >(000domains.com) 24 hours have passed and not even a single > >automated answer has come from them. > > > > Can someone in the US please help us with this? There's a phone > >number to call 800-401-5220. The case ticket number is 01278137. > >If somebody volunteers please write me to send you the account > >credentials. > > Any takers? I can do so, but I don't want to duplicate efforts, as it might > look suspicious with more then two people calling in. Today I login into 000domains to see what happened with the ticket and to my surprise there's an internal error message saying they can't access my case management ticket (this is the attachment). This message gives a different phone number to call [1]. @Roger (or any volunteer): Can you please call this number and ask what the problem is. [1] +1 360-253-2210 Another way to solve the problem may be to point to a working nameserver elsewhere too (the API seems to allow this option). I'll ask Andreas K. whether we can point to the wearlab DNS in the interim. -- Cheers Jorge.-

June 6, 2012