- Dillo-dev - lists.mailman3.com

Weird chars bug
by jcid＠dillo.org Sept. 27, 2009

Sept. 27, 2009

Hi, Since dillo-2.1, enabled-CSS makes funny chars in this page: http://blogdrake.net/node/14916 Screenshot: http://www.dillo.org/test/weirdChars.jpg Disabling it from the tools button solves the problem. Does anybody know what's the problem here? -- Cheers Jorge.-

3 2

Textblock::drawLine() split
by Johannes.Hofmann＠gmx.de Sept. 19, 2009

Sept. 19, 2009

Hi corvid, this split was overdue! Thanks a lot for the cleanup. Cheers, Johannes

1 0

experimental patch: image loading options "same domain", "same host"
by corvid＠lavabit.com Sept. 17, 2009

Sept. 17, 2009

I just put together a somewhat hacky patch to add "same host" and "same domain" for image loading from the tools button (or dillorc) http://www.dillo.org/test/img_loading_options.patch I ran on it as long as I could tolerate images over dialup (not long :), so here it is, and I will clean it up if there is interest shown in getting it into dillo. (I would probably want to change the names of the dillorc choices for image loading, make the internal value into an enum, look at the loadImages/autoload_image code duplication, etc., etc... Oh, and look up how to fix the tools menu width...)

5 11

View page source suggestions
by dennisn＠dennisn.dyndns.org Sept. 16, 2009

Sept. 16, 2009

Currently, the "View page source" right-click context menu isn't available below the rendered html -- so if the actual html page is very small and/or dillo's window is very big, right clicking the bottom half (for example) of the browser does nothing :\. Also, is there a way to have the source viewed in one's preferred text editor? :b (read: gvim)

3 2

[devidfil@gmail.com: [Dillo-dev] Switch to fltk1.3?]
by jcid＠dillo.org Sept. 10, 2009

Sept. 10, 2009

On Sat, Aug 29, 2009 at 01:06:36PM +0200, Johannes Hofmann wrote: > Hi Jorge, > > do you plan to answer this mail? Sorry I've been lost with other activities. > My point here is that we should > stick with fltk2 until there is an official release of fltk1.3. Yes. I agree. We went with unreleased FLTK2 and it has caused lots of problems (despite statical linking). > If there are license issues with fltk2 they should be handled > between debian and the fltk community. Of course we could try to > help. It looks like FLTK2 is quite stalled. Of course we can knock the door again. Maybe this is also a good time to ask for fltk1.3's timeline again. The last time, the optimistic release date was near the middle of 2009. > Date: Sat, 22 Aug 2009 18:40:03 +0200 > From: Devid Antonio Filoni <devidfil(a)gmail.com> > Subject: [Dillo-dev] Switch to fltk1.3? > To: dillo-dev(a)dillo.org > > Hi, > is possible to switch to fltk1.3? I sent a lot of emails to fltk > developers trying to get the license issue of fltk2 > (http://www.fltk.org/str.php?L2198+P0+S-2+C0+I0+E0+Qlicense) fixed but > I still (after months of sent emails) haven't gotten a reply. dillo is > going to be removed from Debian and Ubuntu repositories because it > depends on removed packages and the newest dillo release cannot be > uploaded because fltk2 is not in the repositories and it cannot be > accepted due to the license issue. Is possible to switch to fltk1.3 or > to another toolkit please? > > Thanks, > Devid Antonio Filoni Hi Devid, We plan to switch to fltk1.3 soon. The point is to have a solid release date to start the port. When we started with fltk2 it was supposed to be released soon... :P I'm writing to the fltk1.3 team. Stay tuned. -- Cheers Jorge.-

2 3

nytimes links and redirection
by corvid＠lavabit.com Sept. 5, 2009

Sept. 5, 2009

I'd been in the habit of letting wget retrieve nytimes links, but today I finally fought with it long enought to learn a few things. - wget works because it remembers cookies while redirecting. I was sure that enabling cookies required a flag, but nope. - If I increase the maximum redirect level in dillo, it gets up to 9 before nytimes relents and figures out that I don't want to give it any cookies and provides me with the page. - If I change the www to www10, it works immediately and doesn't bother with redirection at all.

1 0

perhaps an iterator bug
by corvid＠lavabit.com Sept. 3, 2009

Sept. 3, 2009

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

whattheinternetknowsaboutyou
by Johannes.Hofmann＠gmx.de Sept. 3, 2009

Sept. 3, 2009

Hi, this http://wtikay.com/docs/details.html is quite interesting. Dillo is not vulnerable, but we should keep this in mind when implementing background image support. Cheers, Johannes

2 2

horizontal scrolling while searching
by Johannes.Hofmann＠gmx.de Sept. 2, 2009

Sept. 2, 2009

corvid, you have just fixed an issue with horizontal scrolling during search. While testing it I realized, that horizontal scrolling during search does not work at all with plain text. Any idea why? Cheers, Johannes

2 2

Planning
by jcid＠dillo.org Sept. 2, 2009

Sept. 2, 2009

Hi, Here are some pending issues which I've partially sorted by priority (at least the top half). Please add the missing ones and let's try to finish sorting it, with a view to planify our work. * Make DIV-based pages render correctly. This is the most visible rendering fault in Dillo. The textblock doesn't have a way to handle it (not implemented). IIRC I'm willing to dig into it and Johannes will help. e.g. http://www.advogato.org/faq.html * Add blocker (this also has to do with privacy). A full RE-based one may have significant overhead (test required), but simple string-matching may do most of the trick. I've also thought for a long time that a "don't load from other sites" preference may help a lot. The whole topic needs some thought but it's not hard to implement. e.g. doubleclick. * Handle negative values in CSS. e.g. wikipedia. * What will we do with xhtml? To render or not to render... FF doesn't validate. BUG#732 One solution is to add a notification widget area below the control panel that hides/unhides as the find bar, to warn when a xhtml file has detected bugs (we'd also move the meta refresh warning to display here). I already have a simple patch to add xhtml rendering. The widget implemetation is the missing part. It should be much simpler than the close button in each tab. :-) e.g. http://planet.postgresql.org/ * Jump to #anchor doesn't work correctly. It looks like a timing issue, but the idle-call API needs a review as a whole. * dpi for "view page source" (it re-uses search capability). This requires a check of the current data-passing inside DPIP. * Improve the DPI development/debug framework. * https dialog bombing issue. BUG#868 AKA make https dpi a server (i.e. not a filter dpi). * Render bug at http://www.directfb.org/ (and its links). The table has too wide a first column. Back/Fwd solves it. *   handling in fltk.org The relevant point is to define a consistent way to handle whitespace in the textblock. * FTP download doesn't work?! -- Cheers Jorge.-

5 19