- Dillo-dev - lists.mailman3.com

Re: commit 3e01d83fd6d1 draws too large background box
by Johannes.Hofmann＠gmx.de May 9, 2010

May 9, 2010

Hi, sorry for the delay... On Tue, Apr 27, 2010 at 11:40:11PM +0200, Johannes Hofmann wrote: > On Tue, Apr 27, 2010 at 09:04:49PM +0000, corvid wrote: > > > commit 3e01d83fd6d1 (draw background for all Words, not just text) > > > draws a too large background box e.g. in this example: > > > > > > <html><body> > > > foo <div style="background-color: blue; margin-top: 100px">bar</div> > > > </body></html> > > > > > > The margin should not be blue. > > > What is the reason for this change anyway? Shouldn't each widget be > > > responsible for it's drawing (including the background)? > > > > This is when I was looking at the rectangles of color on the fltk.org > > page around, e.g., "FLTK Apps", "FLTK Library"... > > > > The rectangle of color (which came from the style of the A element, iirc) > > is "supposed" to be taller than the little rounded-corner images, judging > > by what firefox does. > > Ah, I think I see the problem now. Textblock has to draw the > background for the <A> element - even at places where it is covered > by child widgets, as they might be transparent. > On the other hand margins are always transparent (see > http://www.w3.org/TR/CSS2/box.html) so there is a problem in the > current implementation. > I guess I need some time to think about this. > > > > > So if the margin is part of the child, then... > > how should this be disentangled? > > Does it come down to being one of those things that have to wait until > > we have more of a real box model? > > > > We already have a proper box model for block boxes, what we are missing > is proper handling of inline boxes (e.g. drawing borders around > <a>-elements). Ok, the general problem is that a single Textblock widget can handle multiple HTML elements. E.g. in this case: <a href=foo style="background-color: red">foo <b>bar</b></a> there is just a single Textblock drawing the whole thing. The style of the word "bar" would normally not have a background color set, but the red of the <a> element would shine through, but as the textblock simply draws one word after the other, we do not draw the whole <a> element and then draw the <b> element on top. To make the background color work nevertheless, I had introduced the inheritBackgroundColor hack, which will pass the red background to the style of the child element (<b> in this case). However, this hack does not work properly if the child element has a margin: <a href=foo style="background-color: red">foo <img src=foo.png alt=bar style="margin:1em"></a> So I think we should remove the whole inheritBackgroundColor() hack and replace it with some code in textblock.cc, that draws the proper background color for all words as necessary. We need to be careful though to not draw word backgrounds if they are the same color as the whole textblock to avoid excessive drawing. This would still not allow things like: <b style="border: 1px solid black">foo</b> but I currently don't see a simple way to make that work. Cheers, Johannes

1 0

[rogerx@sdf.org: Bug in Dillo Text Entry]
by jcid＠dillo.org May 8, 2010

May 8, 2010

-- Cheers Jorge.-

1 0

style.css font-family misses redraw
by dennisn＠dennisn.dyndns.org April 28, 2010

April 28, 2010

If you specify a font-family in ~/.dillo/style.css, such as: * { font-family:sans-serif } And then visit a page like: http://www.linuxfromscratch.org/lfs/downloads/6.6/ ... it will produce "ghost" lines from the previous rendering before the css was applied. Moving the window, or doing anything else that forces a redraw, cleans it up. (Let me know if you don't see this and I can provide a screenshot.)

3 9

image background colors
by corvid＠lavabit.com April 24, 2010

April 24, 2010

Is this anywhere near correct? (This at least makes the background colors right for the rounded-corner images on the top row of links at fltk.org. Of course it still looks funny because valign top isn't obeyed...)

2 4

zero-delay refresh, but no URL
by corvid＠lavabit.com April 23, 2010

April 23, 2010

http://www.algo-prog.info/ocmc/ contains <meta http-equiv="refresh" content="0;web/" /> For refresh, we assume there will be an '=' from "URL=". Since there isn't one, we refresh the same URL over and over and over... We could refuse to follow a zero-delay refresh without a new URL, but I seem to recall back in the never-follow days that sometimes a page _wanted_ to be immediately refreshed once, after which it would provide the contents (I always wondered why). So perhaps the nav redirection stuff should use bw->redirect_level.

2 4

classes and pseudoclasses
by corvid＠lavabit.com April 21, 2010

April 21, 2010

I was looking at how the fltk site appears, and noticed that dillo and firefox have different ideas of what to do for: <html><head><style> A:link {color: #ff0000} A.unsel {color: #000000; background-color: #00ff00} </style></head><body> <a class=unsel href=http://www.dillo.org>a link</a> </body></html>

2 1

Dillo: being removed from Debian
by jcid＠dillo.org April 20, 2010

April 20, 2010

FYI, corvid wrote: > Johannes wrote: > > On Tue, Apr 20, 2010 at 10:14:56AM -0400, Jorge Arellano Cid wrote: > > > On Tue, Apr 20, 2010 at 03:31:47PM +0300, Jari Aalto wrote: > > > > > > > > Dillow in in danger being removed from debian > > > > > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575240 > > > > > > > > This is mostly due to RC bugs (grace, serious, important) listed in: > > > > > > > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=dillo;dist=unstabl > > > > > > > > The current Debian maintainer does not seem to repond any longer, so I > > > > could offer my help to keep the package in Debian: > > > > > > > > Would you take a look at the Debian bug listing and see their > > > > Could be solved or if they already are in latest version? > > > > > > > > Thanks for any help, > > > > Jari > > > > > > I'd be happy if dillo1 is removed from Debian: > > > > > > > > > * It's full of bugs (+ i18n's patch bugs) > > > * Uses GTK1 (this misleads developers, packagers and distros to > > > think that dillo is still a GTK1-based project). > > > * When people hear about dillo, or find our website, they try a simple > > > 'apt-get dillo' and get the wrong picture. Then they find out it > > > haven't had patches in years <-> dead project. Who would like to > > > put his effort into that project? > > > * It states that is not the official dillo and that dillo.org developers > > > should not be bothered with its bugs (my request at the time), but > > > this chains the question: why did the trusty Debian maintainers chose > > > the unnoficial version? There must be problems with the official on > > > * Dillo1 has been unmaintained for years. > > > > > > Then I'd be even happier if we can get dillo/fltk-1.3 into Debian, > > > in the short term. > > > > > > I guess it's easier by first removing dillo1 and then pushing dillo2, > > > but don't know about Debian policies. > > > > > > I'd answer Jari along the above lines, CC'ing dillo-dev. > > > > > > What do you guys think? > > > > I fully agree > > *agrees* -- Cheers Jorge.-

1 0

make instant meta-refresh optional?
by dillo-dev＠toykeeper.net April 16, 2010

April 16, 2010

I was just trying to look up a local place on Google Maps, and found that the page wouldn't render any more. So I investigated, and it turns out to be a combination of two problems: - Dillo now follows instant meta-refresh commands, instead of letting the user decide. - Google Maps redirects to a 'mobile' version of the site, which fails to recognize Dillo's user-agent string and returns WML instead of HTML. (I sent them info about this bug a few moments ago; hopefully they'll fix it) Would it be possible to make that first one optional? Maybe a config variable or something? I liked the old behavior much better. The change was introduced here: changeset: 1037:a72e5506e280 user: Jorge Arellano Cid <jcid(a)dillo.org> date: Sat Apr 18 16:16:18 2009 -0400 summary: Implemented Instant client-side redirects (META refresh with delay=0) For now, I've been building with this small patch: --- a/src/html.cc Wed Apr 07 22:07:07 2010 +0000 +++ b/src/html.cc Wed Apr 14 19:15:12 2010 -0600 @@ -2883,7 +2883,7 @@ mr_url = dStrdup(content); } - if (delay == 0) { + if (0) { /* zero-delay redirection */ html->stop_parser = true; DilloUrl *new_url = a_Url_new(mr_url, URL_STR(html->base_url)); -- Scott

4 7

Dillo's jealous of Google
by onepoint＠starurchin.org April 14, 2010

April 14, 2010

Dillo's *so* jealous of Google it won't let me see it! (So much for the open relationship thing :-) Log attached. I assume that the DENY message is from line 399 of src/capi.c, is that right? This certainly worked only a few days ago. What has changed? It's really not good that Dillo is by default silently denying me access to Google. How can this be improved? Regards, Jeremy Henty

2 2

new fltk snapshot out
by corvid＠lavabit.com April 10, 2010

April 10, 2010

Some compose / input method stuff. http://fltk.org/articles.php?L986 http://fltk.org/newsgroups.php?s4670+gfltk.commit+v4689+T0 If you find it to be an improvement, then we can update the recommendation...

2 1