- Dillo-dev - lists.mailman3.com

duckduckgo

by eocene＠gmx.com

Just tried searching for something using duckduckgo with midori, using the standard search, not the light one. I copied the link URL and saw that they're doing the same thing that google does -- the link URL shown at the bottom of the screen is what you expect, but the link is really a redirection through duckduckgo. Doesn't look like dillo does that -- maybe something to do with javascript, didn't matter why to me. Anyway, I didn't exactly like ddg behaving this way, and I believe I will try using startpage more often instead. (Although I have to turn off CSS to get a next button on startpage results...)

Sept. 5, 2014

configure.in errors

by csoren＠isd.net

> Chris wrote: > > This is from a fresh hg pull, running autogen.sh (or > > aclocal): > > > > configure.in:472: error: AC_SUBST: `src doc' is not a > > valid shell variable name > > configure.in:472: the top level > > autom4te: /usr/bin/m4 failed with exit status: 1 > > aclocal: autom4te failed with exit status: 1 > > > > changing the line AC_SUBST(src doc) to two lines of > > AC_SUBST(src) and AC_SUBST(doc) fixes it. > > That's odd. configure.in moved to configure.ac in late > 2012... > Bad hg syntax on my part, sorry! I fixed it with 'hg update -C`

Aug. 31, 2014

configure.in errors

by csoren＠isd.net

This is from a fresh hg pull, running autogen.sh (or aclocal): configure.in:472: error: AC_SUBST: `src doc' is not a valid shell variable name configure.in:472: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: autom4te failed with exit status: 1 changing the line AC_SUBST(src doc) to two lines of AC_SUBST(src) and AC_SUBST(doc) fixes it.

Aug. 30, 2014

Last hg tip

by jcid＠dillo.org

Hi Sebastian, I'm following closely our hg tip and some things are improving. OTOH the last tip sometimes drops the horizontal scroller bar leaving content out of reach. e.g. [1] [1] http://lwn.net/Articles/609892/#Comments -- Cheers Jorge.-

Aug. 30, 2014

Rendering of illegal widths (incl "px", which used to be legal)

by james.from.wellington＠gmail.com

Hello All, The row of three pictures on this web-page: http://www.avrprojects.net/index.php?view=article&id=61 renders badly in dillo, and differently from Chrome and firefox, because two of them have: width="180px" which the source-code for dillo 3.0.4 (html.cc at about line 1450) tells me used to be legal html, but isn't anymore. Dillo: - reports this as a web bug (with which I agree) - sets the length to auto (which I think means using the default width) To minimise the damage from illegal pages, without hiding the problem, I propose to assume that the numbers in all widths are sensible, and to complain about, but ignore, the trailing garbage. I also discovered that the bug message and another, suppressed, message had type problems, which I have addressed in a way that looks reasonable on osx. My proposed patch is below. Please be aware that Jorge and I started a conversation about whether this was the right thing to do, which wedged. I tested this proposed change by hacking up saved copies of the web-page in various ways. One of them, which makes a mess of the bug message, is attached, but they are not really a clean test-case. I am not aware of any automated test into which this change should be added. If someone can point me toward one, then I will think about how to test it cleanly. Regards, James. ----------------------- $ diff html.cc.orig html.cc 1483,1485c1483,1488 < if (*end && !isspace (*end)) { < BUG_MSG("Garbage after length: %s\n", attr); < l = CSS_CREATE_LENGTH(0.0, CSS_LENGTH_TYPE_AUTO); --- > while (end && isspace(*end)) > ++end; > if (end && *end) { > BUG_MSG("Garbage after length: '%s'; " > "ignoring garbage; using %g (possibly in pixels)\n", > attr, CSS_LENGTH_VALUE(l)); 1489c1492 < _MSG("a_Html_parse_length: \"%s\" %d\n", attr, CSS_LENGTH_VALUE(l)); --- > _MSG("a_Html_parse_length: \"%s\" %g\n", attr, CSS_LENGTH_VALUE(l)); ----------------------- ps I am contemplating getting involved in other trivial rendering problems, and thinking about the todos in dpid/main.c:204 and dpid/main.c:297. My interest in the todos is that dillo functions with gmail, but keeps (de facto) logging me out by discarding my session cookie. Could someone please point me to generic advice about: - which source tree I should be building (Jorge mentioned GROWS, but I don't know what that means) - how to use mercurial to develop multiple patches in parallel and keep them separate, while running a built program that includes all of them ?

Aug. 25, 2014

Stretched out images

by fusionfile＠gmail.com

On 2014-08-10 14:34, Sebastian Geerken wrote: > Nearly correct: all changes to <http://flpsed.org/hgweb/dillo_grows> > are now in the main repository <http://hg.dillo.org/dillo>; the former > is not up to date and misses some fixes, so please use the latter one. > > Keeping aspect ratio of images should work now; if not, this is a bug > to be fixed. Thanks for your effort, Sebastian. I just updated the source to the latest revision (3877) and recompiled Dillo but the problem remains; a Google image search still shows horizontally stretched out images. Any clues? -- August

Aug. 10, 2014

Stretched out images

by sgeerken＠dillo.org

On Sun, Aug 10, 2014, higuita wrote: > Hi > > > make them look *really* ugly. For instance if I do a Google image > > search all images are stretched out horizontally: > (...) > > How can we fix this? > > AFAIK, this is a due missing features in the CSS support. > Current support for floats and grows seems fix this, but is still > incomplete in the main dillo. Try this one with more complete support > until its merged back: > > http://flpsed.org/hgweb/dillo_grows > > It works fine for me using this one. Nearly correct: all changes to <http://flpsed.org/hgweb/dillo_grows> are now in the main repository <http://hg.dillo.org/dillo>; the former is not up to date and misses some fixes, so please use the latter one. Keeping aspect ratio of images should work now; if not, this is a bug to be fixed. Sebastian

Aug. 10, 2014

Stretched out images

by higuita7＠yahoo.co.uk

Hi > make them look *really* ugly. For instance if I do a Google image > search all images are stretched out horizontally: (...) > How can we fix this? AFAIK, this is a due missing features in the CSS support. Current support for floats and grows seems fix this, but is still incomplete in the main dillo. Try this one with more complete support until its merged back: http://flpsed.org/hgweb/dillo_grows It works fine for me using this one. Best regards, 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

Aug. 10, 2014

Stretched out images

by fusionfile＠gmail.com

In the current development version of Dillo (rev. 3873) images are sometimes scaled in a way that doesn't preserve the aspect ratio which make them look *really* ugly. For instance if I do a Google image search all images are stretched out horizontally: http://www.google.com/search?q=test How can we fix this? Regards, August

Aug. 9, 2014

dillo slower than iceweasel on some pages

by eocene＠gmx.com

Andreas wrote: > Hi, > > I made a shocking experience when visiting pages like > http://www.wetteronline.de/wetter/berlin > > hg tip dillo takes 45 seconds. > > The last release takes a few seconds. > Starting a fresh iceweasel I need around 17 seconds. I hope there is > still much room to optimize and there is a possibility to have a fast > browser even with floats. For those times when we just need to get our information quickly -- to fill in the gap while floats/grows are being optimised -- I just copied over the changes since 3.0.4 that don't involve floats or grows into http://flpsed.org/hgweb/eocene_persistent_connections/ I didn't try to be exceedingly careful when doing this, but it appears to be working so far.

Aug. 6, 2014