- Dillo-dev - lists.mailman3.com

is dillo ready for load_background_images=YES in a release?

by eocene＠gmx.com

Once you know that load_background_images can be toggled from the menu, it's good, but our css/rendering is still incomplete enough that background images obscure text rather frequently. I think load_background_images=YES by default may make the experience of trying out dillo a negative one.

April 5, 2014

background images and display:none

by eocene＠gmx.com

Johannes wrote: > On Fri, Apr 04, 2014 at 05:37:52PM +0000, eocene wrote: > > > > I was checking what was causing the "IO_write, closing with pending data > > not sent" messages with background images, and at least in the case that > > I just dug into, it was due to display:none. Is this considered > > expected behaviour, or a bug, or...? > > The simple case can be prevented with something like in attached > patch. But even with this patch I see quite some of the messages you > mention. So there must be something else going on too. It might be that elements with display:none are fixed now but elements whose ancestors are display:none are still broken.

April 4, 2014

background images and display:none

by jcid＠dillo.org

On Fri, Apr 04, 2014 at 05:37:52PM +0000, eocene wrote: > > I was checking what was causing the "IO_write, closing with pending data > not sent" messages with background images, and at least in the case that > I just dug into, it was due to display:none. Is this considered > expected behaviour, or a bug, or...? An "informative" message. When the socket has already received the request string and has asked the kernel to deliver it, but it has not got out fully yet, and suddenly the socket gets cancelled/aborted, the message is displayed. Whether expected behaviour or a bug, depends on the case. -- Cheers Jorge.-

April 4, 2014

background images and display:none

by Johannes.Hofmann＠gmx.de

On Fri, Apr 04, 2014 at 05:37:52PM +0000, eocene wrote: > > I was checking what was causing the "IO_write, closing with pending data > not sent" messages with background images, and at least in the case that > I just dug into, it was due to display:none. Is this considered > expected behaviour, or a bug, or...? The simple case can be prevented with something like in attached patch. But even with this patch I see quite some of the messages you mention. So there must be something else going on too. Cheers, Johannes

April 4, 2014

background images and display:none

by eocene＠gmx.com

I was checking what was causing the "IO_write, closing with pending data not sent" messages with background images, and at least in the case that I just dug into, it was due to display:none. Is this considered expected behaviour, or a bug, or...?

April 4, 2014

dillo-3.0.4-rc1 available for testing

by Johannes.Hofmann＠gmx.de

Hi, thanks to Andreas Kemnade who helped us resolving our server issues and even provides hosting on a new system, we can finally provide the first release candidate for dillo-3.0.4. It can be downloaded from http://www.dillo.org/download/dillo-3.0.4-rc1.tar.bz2 Please test it and report back. Cheers, Johannes

April 4, 2014

css charset broken

by johannes.hofmann＠gmx.de

On Tue, Mar 25, 2014 at 09:36:39AM +0400, Georgiewskiy Yuriy wrote: > > Hi all, seems there is a bug in css parsing in latest dillo 3.0.3 and latest HG too: > > If i have load_stylesheets and/or (site depends) parse_embedded_css > eq YES in dillorc a number of russian sites with css renders with > broken encoding, for example www.yandex.ru, > www.rambler.ru, if i disable css all renders fine with proper russian encoding. I guess CSS is switching the font to something that doesn't support Cyrillic. E.g. on yandex.ru I see: body{font:.8em Arial,Helvetica,sans-serif;} So if you don't have Arial installed, it will switch to Helvetica and that - at least here - doesn't cover Cyrillic. You can test this with attached HTML. You could try to get Arial installed. In the long run Dillo or fltk should implement some fallback mechanism if glyphs are missing in the selected font. Cheers, Johannes

March 25, 2014

css charset broken

by bottleman＠icf.org.ru

Hi all, seems there is a bug in css parsing in latest dillo 3.0.3 and latest HG too: If i have load_stylesheets and/or (site depends) parse_embedded_css eq YES in dillorc a number of russian sites with css renders with broken encoding, for example www.yandex.ru, www.rambler.ru, if i disable css all renders fine with proper russian encoding. C ????????? With Best Regards ???????????? ????. Georgiewskiy Yuriy +7 4872 711666 +7 4872 711666 ???? +7 4872 711143 fax +7 4872 711143 ???????? ??? "?? ?? ??????" IT Service Ltd http://nkoort.ru http://nkoort.ru JID: GHhost at icf.org.ru JID: GHhost at icf.org.ru YG129-RIPE YG129-RIPE

March 25, 2014

[OT] Render proxy for HTML

by rogerx＠sdf.lonestar.org

> On Sun, Mar 23, 2014 at 01:05:47PM -0300, Alan Carvalho de Assis wrote: >Hi Dillors, > >Maybe it could be useful for people willing to browser "modern" sites >with html3/4 browsers: > >http://virtuallyfun.superglobalmegacorp.com/?p=3866 Nothing like getting hit in the face with the obvious. To reiterate, the above URL points to an article instructing users of ancient browsers that they can route the newer (nowadays) formated unrenderable HTML pages through a proxy and render to HTML 3.x or other more capable HTML version viewable by the ancient web browsers. (ie. Setting up a conversion pipe.) -- Roger http://rogerx.freeshell.org/

March 23, 2014

[OT] Render proxy for HTML

by acassis＠gmail.com

Hi Dillors, Maybe it could be useful for people willing to browser "modern" sites with html3/4 browsers: http://virtuallyfun.superglobalmegacorp.com/?p=3866 BR, Alan

March 23, 2014