- Dillo-dev - lists.mailman3.com

Display bug introduced in rev. 2368

by Johannes.Hofmann＠gmx.de

Hi Alexander, On Sat, Mar 31, 2012 at 11:04:26AM +0200, Alexander Voigt wrote: > Dear Dillo developers, > > I just noticed a minor page rendering issue, which was introduced in > revision 2368: The "I'm Feeling Lucky" button at google.com is no more > visible. > > How to reproduce: > ================ > > (1) hg update -r 2367 > (2) visit google.com and note the "I'm Feeling Lucky" button > (3) hg update -r 2368 > (4) visit google.com and note the absence of the > "I'm Feeling Lucky" button > > I noticed this issue with the german google page (google.de) but I > think it also happens on the US variant (google.com) Thanks for the detailed bug report. I backed out the inline-block support until this is resolved. Cheers, Johannes

April 7, 2012

Suggestion regarding XHTML handling

by singpolyma＠singpolyma.net

Somebody claiming to be Johannes Hofmann wrote: >On Fri, Mar 23, 2012 at 10:54:35PM -0500, Stephen Paul Weber wrote: >> Might I suggest actually doing basic namespace handling when a page is >> delivered using an XML MIME type? >> ... instead of seeing the Atom as something it >> cannot process or otherwise handling it, the rendering engine just turns all >> the tags into inline flow content and shows the text contents in what is >> essentially line noise. >> >I don't see what could be done differently here. Firefox renders it >pretty much the same way as Dillo does. Am I missing something? Yes, but that doesn't mean dillo can't be better than firerox :) Stuff from a namespace we understand (right now just XHTML, but in the future maybe SVG, MathML, whatever. or not) should get processed according to the rules of that namespace. Namespaces we don't understand, and for which we have no processing rules, should be ignored completely. And, I feel that if a server is serving with an XML MIME-type, we can trust that they expect XML-style processing rules like this, since tagsoup sites are not served with such a MIME. -- Stephen Paul Weber, @singpolyma See <http://singpolyma.net> for how I prefer to be contacted edition right joseph

March 31, 2012

Display bug introduced in rev. 2368

by Hole.destructor＠gmx.de

Dear Dillo developers, I just noticed a minor page rendering issue, which was introduced in revision 2368: The "I'm Feeling Lucky" button at google.com is no more visible. How to reproduce: ================ (1) hg update -r 2367 (2) visit google.com and note the "I'm Feeling Lucky" button (3) hg update -r 2368 (4) visit google.com and note the absence of the "I'm Feeling Lucky" button I noticed this issue with the german google page (google.de) but I think it also happens on the US variant (google.com) Kind regards, Alexander

March 31, 2012

Suggestion regarding XHTML handling

by Johannes.Hofmann＠gmx.de

On Fri, Mar 23, 2012 at 10:54:35PM -0500, Stephen Paul Weber wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Might I suggest actually doing basic namespace handling when a page is > delivered using an XML MIME type? For example, this page: > <http://aggregator.singpolyma.net/feeds/denver/> contains both XHTML and > embedded (namespaced) Atom, but instead of seeing the Atom as something it > cannot process or otherwise handling it, the rendering engine just turns all > the tags into inline flow content and shows the text contents in what is > essentially line noise. > > I know that in a "normal" HTML page you want the heuristics to do this sort > of thing in case some bozo has dumped something that maybe looks like a > namespace into the tag soup (and namespaces aren't officially supported in > HTML anyway), but if the MIME-type is an XML one, the UA should be able to > process it as XML and ignore or otherwise handle namespaces it doesn't > understand. I don't see what could be done differently here. Firefox renders it pretty much the same way as Dillo does. Am I missing something? Cheers, Johannes

March 29, 2012

Compiling on wheezy

by abe＠deuxchevaux.org

Hi, On Tue, Mar 27, 2012 at 04:35:23PM -0300, Jorge Arellano Cid wrote: > FYI, the last Debian wheezy update requires -fPIC for dillo > to compile (at least in my 64bit machine). Yeah, and it seems to happen on amd64 (x86_64) only so far: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664949 > CFLAGS="-g -O0 -fPIC" CXXFLAGS="-g -O0 -fPIC" ./configure --enable-ssl Adding CPPFLAGS=-fPIC sufficed for me. We're still investigating why it's actually problem and wasn't one about a month ago... Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | abe at deuxchevaux.org (Mail) X See http://www.asciiribbon.org/ | abe at noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)

March 27, 2012

Compiling on wheezy

by jcid＠dillo.org

Hi there, FYI, the last Debian wheezy update requires -fPIC for dillo to compile (at least in my 64bit machine). e.g. CFLAGS="-g -O0 -fPIC" CXXFLAGS="-g -O0 -fPIC" ./configure --enable-ssl HTH. -- Cheers Jorge.-

March 27, 2012

dillo on maemo

by Johannes.Hofmann＠gmx.de

here is a nice video showing Dillo on maemo: http://youtu.be/v2jH_PXeA2A Cheers, Johannes

March 26, 2012

Suggestion regarding XHTML handling

by singpolyma＠singpolyma.net

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Might I suggest actually doing basic namespace handling when a page is delivered using an XML MIME type? For example, this page: <http://aggregator.singpolyma.net/feeds/denver/> contains both XHTML and embedded (namespaced) Atom, but instead of seeing the Atom as something it cannot process or otherwise handling it, the rendering engine just turns all the tags into inline flow content and shows the text contents in what is essentially line noise. I know that in a "normal" HTML page you want the heuristics to do this sort of thing in case some bozo has dumped something that maybe looks like a namespace into the tag soup (and namespaces aren't officially supported in HTML anyway), but if the MIME-type is an XML one, the UA should be able to process it as XML and ignore or otherwise handle namespaces it doesn't understand. - -- Stephen Paul Weber, @singpolyma See <http://singpolyma.net> for how I prefer to be contacted edition right joseph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJPbUV7AAoJENEcKRHOUZze+aMQAKDSNe3QZzzsIFYZkH2fvWE+ 03gRZy7XtwzqQMBQENAuZgK1orUGR8KO8t69re7f+GFTed36lE5QrqtY2tKPmtrl BD0W7d0bbZpAzIk0akS44l9+ICy2X+iKMxhdzeELcEABxlRLqfgYwS3zZ+XjvOyK VGOj8ejDs1n4G2SO6IC28DXJxa8cijkhfN7QzAO1rUpHSlPV8xO6vCIOultr05Nc VoybKhBTetDV4FsRX4hpwd5/ToAl6JYWvkwaSEny7Pc30H8EXthIzASnf+K2rPwh v31aNWJgrf6DwXhnX1SZLYYFkePpuiLzOAWGbljacJlnkI9r6guXDUIq0U0mCdLD G1fuvnaLCSv78yz7MwDS/hDwxx7rElXk3w7BbwzA71tbuJocBTq3clX4Ho+dL84L +pYCXWjWbt5BPiIgHDiPzj+48AS4kvW9y4a/yCPoAJFExZDdoNdSlFGUvGmc2xwa 9Rcvz7lX6DQ5iZXXBLpVi5IrwMFEaXKd+0dUbsaXD30a6n6r+8o6sDMSh+CIDu20 dVhB58ff7j7cwVsPSQtHZmkjq4x3KxMiIm/gtYijkxh48lsUwMiyIBpw76gUZDPp N22Q4c5bGiHWRUhYHTwuu1C04Dx0wHeWoaKDGaPV9YyEyPq1EiZZTz2Vzd7AMbUT K1x3M4Fep0SUuLsVusle =ldnT -----END PGP SIGNATURE-----

March 24, 2012

thanks for display:block

by Hole.destructor＠gmx.de

Hi Jorge. > Since what dillo version do you see differences? > Could you please post a few example URLs? The improvements were introduced in revision 2357. So, if I update to revision 2356 (`hp update -r 2356') the yellow LaTeX code bits (within a <pre> environment) on the page http://iktp.tu-dresden.de/~avoigt/feynmf.xhtml does not look so nice (there is no border around the code field and the yellow background field color is not rectangular). If I update to revision 2357 (`hp update -r 2357') these code bits are surrounded by a border (as intended) and the yellow background has the form of a rectangle, as it should be. Kind regards, Alexander

March 21, 2012

DNS code changes

by Johannes.Hofmann＠gmx.de

On Tue, Mar 20, 2012 at 06:07:08PM +0100, Georg Potthast wrote: > Sorry for posting three times I had the impression my emails got > lost somehow. It seems there was some issue with the mailing list. > > DOS is basically a single-tasking system. So you cannot fork a new > process and threads do not work well. A thread, as it is currently > implemented for DOS/DJGPP, should yield when it is done and a > different thread can continue. So I try to avoid threads and use > function calls instead if I can. We still use threads only for asynchronous DNS resolution and this can be disabled as before with --disable-threaded-dns. Let us know if there are new issues with the currently committed version. Cheers, Johannes

March 20, 2012