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

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

Re: patch: media_type pref
by corvid＠lavabit.com Aug. 5, 2009

Aug. 5, 2009

Jorge wrote: > On Mon, Feb 16, 2009 at 05:37:36AM +0000, corvid wrote: > > It makes more sense to have a pref that the user can > > control than for us to guess what they might like > > based on screen size or whatever, I think. > > I hesitate on this. For instance: if media_type is defined to > "handheld" and there's no such remote CSS, at least it should > fallback to "screen". If there is a handheld style sheet available and dillo is running on a handheld, it would be a shame not to use it. I'm hoping that the page author would have the sense to supply something for type "all". > Maybe it's more practical to provide custom stylesheets (as the > current "style.css". e.g. small_screen.css, print.css) and to > allow switching among them from the "Tools" menu. > > What do you think? I think someone using handheld would want to use both the page author's handheld-specific code and a user style suitable for their device. I'll send this to the list in case anyone with experience using such devices with the web has opinions to share.

3 3

dillo 2.1]
by sandshrew＠gmail.com July 4, 2009

July 4, 2009

Accidentally sent to corvid only. Forwarding to dillo-dev. > > > It seems whoever designed the new website theme has no idea what > > > READABILITY means... It looks like someone just used some stupid online > > > color picker, which just picks some similar colors to the one user > > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > > regression... > > > > Hm I like the new design, but I agree that readability might be a problem. > > Let's see what other say. > > I still find visited text to be hard to read, but I know I should > break down and get a new display... > I wonder if you are the only dillo user with old display... BTW, I am using pretty new LCD display and still find it hard to read.

4 7

Feels good to be free. Close-tab button.
by jorl17.8＠gmail.com June 30, 2009

June 30, 2009

Well, I promised I would report to you when I got more free time. Guess what, I'm on vacation! Getting free time from my own personal projects finally lets me take a closer look at Dillo. I am sorry for being away for such a long time, though. I would like to contribute to one area that I have contributed previously -- the close-tab button. It isn't critical, I know, but, for now, it's the best I can do. The idea now is to finally have a button in each tab. It is tough, but I am getting somewhere. The 'initial' drawing part is done, but I have had to make some small changes to some virtual functions, and also changing non-virtual functions and finding a way to 'enable' them in the code. It's pretty hackish right now, but I have managed to print the button and am now starting to handle all the events and different button states (clicked, over, etcetera). I'll keep you updated! Jo?o

1 0

[PATCH] warning: ignoring return value of ‘int chdir(const char*)’
by newman.x＠gmail.com June 27, 2009

June 27, 2009

gcc-4.4.0-4.i586 HG tip: newman src $ make | grep -i warning [...] paths.cc: In static member function ?static void Paths::init()?: paths.cc:38: warning: ignoring return value of ?int chdir(const char*)?, declared with attribute warn_unused_result With the patch dillo-guard-chdir.patch no warning. But this patch alone won't have any effect, all MSG(...) from Paths::init() won't write anything to output due to prefs.show_msg not being set to TRUE at that moment. Patch dillo-use-MSG-asap.patch moves a_Prefs_init() before Paths::init() is called. Hope it's not breaking anything. Tested - setting non-existing directory instead of /tmp - Dillo won't crash on start, basic browsing works -- Regards, Michal Nowak

3 4

[marcio.ccamargo@gmail.com: Thank u!]
by jcid＠dillo.org June 25, 2009

June 25, 2009

Hi, :) -- Cheers Jorge.-

1 0

patch: save bookmark segfault when dpis not found
by corvid＠lavabit.com June 24, 2009

June 24, 2009

A new one seen in the bugtracker... a_Bookmarks_chat_add() sets URL to NULL, so it needs to be handled. Anyway, the reason this is interesting is that I had always figured the URL_*() macros were protecting against a NULL URL, when really they protect against NULL fields in URLs.

2 2

patch: viewport keybindings
by corvid＠lavabit.com June 24, 2009

June 24, 2009

Here is an idea for viewport keybindings. It just builds a SimpleVector once and lets all of the viewports point to it, which I think goes against the dillo/dw boundary rules, but we'll see how the general idea goes over...

2 1

patch: a binding for stop
by jcid＠dillo.org June 24, 2009

June 24, 2009

On Fri, May 29, 2009 at 02:39:04AM +0000, corvid wrote: > > I don't like much Esc for stop, but if that's FFs default, > > it may be better than another (as the Ctrl-x clash you spot). > > Afterall this is what configurable keybindings is suppossed to > > solve so Esc is OK for me as default. > > I'll have to rip out the mysterious HIDE_PANELS in order to > take back Escape which it is using. AFAIS, in the sense of: > What is the purpose of KEYS_HIDE_PANELS when we have KEYS_FULLSCREEN? The idea is to handle the case of a "search text" request on hidden panels. In which case the search panel is temporarily shown, until Esc is pressed. If it can be done with less variables, no problem. Now, Esc is used to: - Close dialog windows - Hide the search panel Please don't rip that functionality. The idea is Esc to stop when there's no search bar. -- Cheers Jorge.-

2 3

dillo 2.1
by sandshrew＠gmail.com June 24, 2009

June 24, 2009

Been testing dillo 2.1 for some time and would like to share my experience. It's really great to see some basic css support (appearance of most if not all websites has improved alot), properly resized images, redirection and basic authentication working now :) Anyway, even dillo improved alot recently there still seems to be some issues. Here are some I've noticed after testing this release for few days: Rendering 1) ubuntu.lt Not sure if it's dillo fault or website's malformed stylesheet, but with default dillo settings some of the lithuanian characters are not displayed. This can be fixed by just adding "* {font-family: serif !important}" to the style.css. Here is a pic with some of the places where letters are missing marked in red: http://img4.imageshack.us/img4/2227/ubuntult.png 2) gmail It's nice that login works now, but with default dillo settings the size of most of the text is 1px. This can be partially fixed by adding font_min_size to dillorc, but it's obviously a dillo bug as this doesn't happen with links-hacked. 3) google What's with the textarea in the top left corner of the page? And just for information: signing out doesn't work because it requires basic javascript support (works with links-hacked). 4) Black on black, white on white... http://www.nma-fallout.com/forum/viewtopic.php?t=42776&start=2660&sid=a5712… For some reason black font color is used here and we get black text on black background in some posts (doesn't happen with links-hacked). http://www.acetoneteam.org/ Background color is not set here and if we have "body {background-color: white}" rule in our style.css file, we get white text on white background. 5) http://ubuntuforums.org/showthread.php?p=6592005 What's with the PINK blocks? If that's more of a "feature" then a bug, can the color be changed by using some css rule? 6) http://www.binaryworld.skynet.lt/DUK.html If we use one link with fragment identifier in the page, all the others are marked as visited too. 7) Authentication Basic authentication does work now, but at first the server displays a message saying "wrong credentials or browser doesn't understand how to supply the credentials" and only then a window pops up asking for the credentials... UI 1) Positioning the tab close button on the top RIGHT corner of the browser isn't a good thing because: a) The distance between the most commonly used buttons and the tab close button is pretty big (especially when widescreen monitors are pretty common nowadays); b) It only allows closing the active tab; I think it would be much better if all tabs had close buttons or at least the button was placed near the last tab. 2) Trivial but... because the setting to enable/disable image loading now is in the wrench menu it is two clicks away instead of one as it used to be in dillo 2.0. Maybe css settings could be left where they are now, but the setting for enabling/disabling images could be moved where it was in dillo 2.0? 3) UPPERCASE letters should be used in the File menu to define keyboard shortcuts, because now L looks like I (Open url... ctrl+l) 4) Don't you think "Are you sure you want to close the browser?" message is pretty annoying? Other: It seems whoever designed the new website theme has no idea what READABILITY means... It looks like someone just used some stupid online color picker, which just picks some similar colors to the one user chooses. The old website looked MUCH MUCH better. Imho, it's a regression... PS: how to install dillo 2.1 claws-mail plugin? -- Brain: an apparatus with which we think we think. - A. Bierce

4 10