February 2009 - Dillo-dev - lists.mailman3.com

perhaps an iterator bug
by corvid＠lavabit.com 03 Sep '09

03 Sep '09

I was trying the new search functionality a bit more and found this (it's also present in my Dec 2008 dillo*). With the page: <table> <tr><td>no close-tr <tr><td>has a close-tr</tr> <tr><td>here's another line</tr> </table> if I search for "rh", it finds one instance of it split between the second and third table rows. * My older dillos were lost in a tragic "I don't think I need my CVS stuff anymore" accident.

3 4

[patch] Improving keyboard shortcuts for tab navigation
by tim.nieradzik＠gmx.de 13 Jun '09

13 Jun '09

This patch adds keyboard shortcuts for the tabs 0 - 9. You can reach them by pressing Ctrl concurrently with the number number of the tab you would like to see. Thus, for the first tab this is Ctrl-0. Alternatively, you can press Ctrl-Home. To get to the last tab, simply press Ctrl-End. In addition the modifier for moving left and right between tabs has been changed from Shift to Ctrl because it makes sense to have an unified modifier for all tab movement operations. --Tim

7 51

experimental patch: Re: dillo2 wrapping Chinese
by corvid＠lavabit.com 06 Jun '09

06 Jun '09

dillo people: It turns out that dillo handles Chinese quite badly because the text doesn't contain whitespace (BUG 827). It looks like Japanese is that way as well. 1) People using East Asian languages: Does this do roughly the right thing? I've read that there are picky rules about certain individual characters, but I just mean in general here. 2) Thoughts on optimization are welcomed. littlebat: For some reason, I was thinking that whitespace was required between words in dillo, but I misremembered. littlebat wrote: > Hi, > Thanks for the work on Dillo. > > I think it isn't a good idea to resolve long chinese line wrapping > problem by inserting space after punctuation mark("?" or "?" or "?", > etc..). > > Here is a "Dillo2 Wrap Long Chinese Line Test" page: > http://www.learndiary.com/en/dillo2-wrap-long-chinese-line-test.htm . > Open it with Firefox or IE, then open it with Dillo2, You will see the > different of wrapping long chinese line between them. > > Note, unlike english, there is no space between Chinese characters. So, > it should be wrapped after any Chinese character which has reached the > end of a line. I don't know the technique detail about this, but, I > think, let the Chinese characters function as (english) commas or > periods is a good idea, so, a new line can be started after any Chinese > charcter which character has reached the end of a line. > > littlebat > > http://www.learndiary.com/en/ > > > corvid wrote: > >Would it make things better or worse than it is now if I inserted a > >space when encountering a "?" or "?" so that dillo would know > >that it can wrap there? If that doesn't show up properly, > >I mean the characters that function as commas and periods. > > > >(I'm trying to think of something simple that will at least help you > > somewhat without having to make big changes right now :) > > I realize that it _should_ be able to wrap after most CJK characters, > > but...) > > > >It could be worse because > >1) Those spaces would still be there if you were copying and pasting > > the text to something else. > >2) If you wanted to search a page for "text?text", you would have to > > enter "text? text" with a space in there.

3 10

google login redirect
by furaisanjin＠gmail.com 27 Mar '09

27 Mar '09

Hi all. I have noticed that google login redirect is something like this. <meta http-equiv="refresh" content="0; url='http://www.google.com/ .....> So generated redirect template looks like <table width='100%'><tr><td bgcolor='#ee0000'>Warning:</td> <td bgcolor='#8899aa' width='100%'> This page uses the NON-STANDARD meta refresh tag.<br> The HTML 4.01 SPEC (sec 7.4.4) recommends explicitly to avoid it.</td></tr> <tr><td bgcolor='#a0a0a0' colspan='2'>The author wanted you to go <a href=''http://www.google.com/ ... So dillo just navigates to the same page. This is the reason why we can't login. Regards, furaisanjin

4 10

Ohloh does not accept http://hg.dillo.org/dillo as Enlistment for the Dillo browser.
by wine.dev＠web.de 25 Mar '09

25 Mar '09

Hi. Thanks for working on Dillo. I tried to update the Dillo Project Page on Ohloh, but the the repository failed on the id command. ...$hd id http://hg.dillo.org/dillo abort: cannot look up remote revision; remote repository does not support the 'lookup' capability! Which Mercurial version is used to serve dillo? -- By by ... Detlef

3 6

My valgrind logs, for all to see.
by onepoint＠starurchin.org 17 Mar '09

17 Mar '09

For your information. http://starurchin.org/dillo/valgrind.html It lists the valgrind errors from my most recent Dillo sessions. It's just one big static HTML page at the moment. Feel free to suggest how it could be more useful. You can see we're still getting lots of small leaks from the CSS parser, though the big ones have been fixed by recent commits. Regards, Jeremy Henty

3 16

Holiday week
by jcid＠dillo.org 11 Mar '09

11 Mar '09

Hi there, I happen to be enjoying a much needed holiday week! :-) The plan is to come back around near wednesday 25. In the meanwhile, I leave you with the following issues lurking in my list to be considered. Maybe all of them can be left to the release after 2.1, but maybe not: [ ] https dialog bombing issue. BUG#868 When enabled, multiple https requests to the same site result in dialog bombing. The https dpi is disabled by default in Dillo. Anyway, in Debian, there's a security warning against dillo for not checking certificates (I don't know what version of dillo they use, nor why they enable https.) [ ] Jump to #anchor doesn't work correctly. The idle timeout doesn't work reliably (an old bug). [ ] Implement @import statement in STYLE element. [ ] What will we do with xhtml? FF doesn't validate. BUG#732 This would be interesting to define. (already suggested as discussion material in another thread). [ ] "-fno-rtti -fno-exceptions" gcc: 64KB less. Enabling this switches reduces the binary size. [ ] dpi for "view page source" (it re-uses search capability). Waiting since a long time... [-] BUG#892 prefs bg_color is not working Johannes was working on related things... [ ] META refresh: "instant client-side redirect". [ ] META refresh: URL='<URI>' case. I plan to implement both when I'm back (and to include them in dillo-2.1). BTW, I want to welcome Tim Nieradzik as a new developer and to tell Joao that the bug in the find-text iterator is not that much important. Just focus on something more urgent. -- Cheers Jorge.-

4 5

Re: css parsing numbers
by Johannes.Hofmann＠gmx.de 03 Mar '09

03 Mar '09

On Fri, Feb 27, 2009 at 03:29:55PM +0000, corvid wrote: > > On Fri, Feb 27, 2009 at 02:26:03PM +0000, corvid wrote: > > > > Committed. I hoped to be able to make that code a bit shorter, but > > > > could not find a reasonable solution... > > > > > > Yeah. In any case, it's just going to get worse/rearranged again > > > for negative numbers... > > > > Exactly. I started my simplification attempts, added negative number > > support - and blew it all up :) > > I'm really considering a flex based scanner now. What do you think? > > I only touched flex very briefly for a class at school long ago, > and I don't remember anything from the experience, but the > idea interests me since it has to be less trouble than trying > to do it by hand... > I think we just need to try it. Attached is a minimal standalone example based on the "Lexical scanner" from the appendix of the CSS 2.1 spec. To compile it use: flex cssscanner.l gcc -o cssscanner lex.yy.c -lfl It reads from stdin. Cheers, Johannes

2 7

patches, bundles, etc
by dillo-dev＠toykeeper.net 02 Mar '09

02 Mar '09

BTW, what's the policy on submitting sizable changes with multiple revisions, such as the configurable keybindings? Is it okay to send a changeset bundle, or do the changes need to be flattened into a single patch? It probably doesn't matter for small changes, but it might be nice to include the history for large changes. -- Scott

7 8

[patch]: remove the workaround for FLTK bug #2084.
by onepoint＠starurchin.org 02 Mar '09

02 Mar '09

The dillo source includes a workaround for FLTK bug #2084[1] which was fixed in revision 6507. We currently recommend[2] revision 6525 or later. There's no need to include this workaround any more, so let's remove it. Regards, Jeremy Henty [1] http://www.fltk.org/str.php?L2084 [2] http://www.dillo.org/source.html

2 1