April 2016 - Dillo-dev - lists.mailman3.com

image overlaps text

by nick＠linicks.net

On 29/04/16 16:46, Alexander Voigt wrote: > I noticed, that in current Dillo (tip) there are cases where images > overlap surrounding text, making in unreadable. Here is an example page: > > https://netzpolitik.org/2016/massenbeschlagnahme-von-mobiltelefonen-in-leip… Strange, renders here OK (latest hg pull). Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

April 29, 2016

image overlaps text

by sgeerken＠dillo.org

On Fr, Apr 29, 2016, Alexander Voigt wrote: > I noticed, that in current Dillo (tip) there are cases where images > overlap surrounding text, making in unreadable. Here is an example page: > > https://netzpolitik.org/2016/massenbeschlagnahme-von-mobiltelefonen-in-leip… Yes, I noticed this already several times on netzpolitik.org. Unfortunately, these cases are not always reproducable. The highest percentage I've found so far on this page: http://www.nachdenkseiten.de/?p=33180 It's at the top on my todo list. Sebastian

April 29, 2016

image overlaps text

by Hole.destructor＠gmx.de

I noticed, that in current Dillo (tip) there are cases where images overlap surrounding text, making in unreadable. Here is an example page: https://netzpolitik.org/2016/massenbeschlagnahme-von-mobiltelefonen-in-leip… Best regards, Alex

April 29, 2016

Dillo_grows merged

by eocene＠gmx.com

On Sun, Apr 24, 2016 at 09:15:42PM +0200, Sebastian Geerken wrote: > On Tue, Apr 19, 2016, eocene wrote: > > > > Here's a segfault backtrace that I just got: > > > > #0 0x080ab83d in dw::Textblock::sizeRequestReference (this=0x955e260, > > index=-1224641713) at textblock.cc:423 > > #1 0x080bcd63 in dw::oof::OOFAwareWidget::OOFAwareWidgetIterator::numParts ( > > this=0x9e446a8, sectionIndex=-1, numContentsInFlow=0) > > at oofawarewidget_iterator.cc:84 > > I do not understand what has actually happens (look at the code). Did > you compile dillo with -O2 or -O0? Can you provide a test case how > this is reproduced? > > Perhaps this is related to another prolem: valgrind prints some > warnings, which neither make sense to me. As I recall, I was double-checking whether the textarea row attr default was still 2 in html5 (https://www.w3.org/TR/html51/sec-forms.html#the-textarea-element) searching for "rows ". But when I try this again, it doesn't crash. FWIW, I compiled with -O0. *tries valgrind* I do get a number of "Conditional jump or move depends on uninitialised value(s)" when the page loads. Searching the page doesn't cause any more, though.

April 24, 2016

https://www.google.com/search?ie=UTF-8&oe=UTF-8&q=dillo

by nick＠linicks.net

Hi Seb, On 24/04/16 12:24, Sebastian Geerken wrote: > Hi! > > Since we do not have a tracking system, I suggest a new thread for > every issue, with some identifier (e. g. a URL) as subject. Please > focus on regressions: bugs not present in dillo 3.0.5. > > As for <https://www.google.com/search?ie=UTF-8&oe=UTF-8&q=dillo>, the > problem are floating inline-blocks (see Johannes' posting and my > answer). Floats positioned side by-side are not an issue for the next > release, so I see two possibilities: > > 1. Leave it as it is, and start on an other positioning after the next > release. > > 2. Deactivate inline-blocks for the next release, and re-activate as > soon as side-by-side positioning of floats is implemented. This > way, dillo 3.1 would render Google like 3.0.5. > > The latter is rather simple: > > diff -r 7c2e27119432 src/html.cc > --- a/src/html.cc Sun Apr 24 12:21:07 2016 +0200 > +++ b/src/html.cc Sun Apr 24 13:23:10 2016 +0200 > @@ -4036,7 +4036,7 @@ > Html_display_block(html); > break; > case DISPLAY_INLINE_BLOCK: > - Html_display_inline_block(html); > + //Html_display_inline_block(html); > break; > case DISPLAY_LIST_ITEM: > Html_display_listitem(html); > > What do you think? Magic! That also fixes the big gaps where adverts are placed, i.e.: http://www.boards2go.com/boards/board.cgi?user=dharrison I like it - and as you say, once the other implementation is done, turn it on again. Gets my vote, and I am running with it now :) Thanks, Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

April 24, 2016

https://www.google.com/search?ie=UTF-8&oe=UTF-8&q=dillo

by sgeerken＠dillo.org

Hi! Since we do not have a tracking system, I suggest a new thread for every issue, with some identifier (e. g. a URL) as subject. Please focus on regressions: bugs not present in dillo 3.0.5. As for <https://www.google.com/search?ie=UTF-8&oe=UTF-8&q=dillo>, the problem are floating inline-blocks (see Johannes' posting and my answer). Floats positioned side by-side are not an issue for the next release, so I see two possibilities: 1. Leave it as it is, and start on an other positioning after the next release. 2. Deactivate inline-blocks for the next release, and re-activate as soon as side-by-side positioning of floats is implemented. This way, dillo 3.1 would render Google like 3.0.5. The latter is rather simple: diff -r 7c2e27119432 src/html.cc --- a/src/html.cc Sun Apr 24 12:21:07 2016 +0200 +++ b/src/html.cc Sun Apr 24 13:23:10 2016 +0200 @@ -4036,7 +4036,7 @@ Html_display_block(html); break; case DISPLAY_INLINE_BLOCK: - Html_display_inline_block(html); + //Html_display_inline_block(html); break; case DISPLAY_LIST_ITEM: Html_display_listitem(html); What do you think? Sebastian

April 24, 2016

GROWS fixes

by jcid＠dillo.org

Hi, On Sat, Apr 23, 2016 at 05:33:53PM +0100, Nick Warne wrote: > Hi Seb, > > On 23/04/16 17:04, Sebastian Geerken wrote: > >Hi! > > > >After the recent changes, dillo handles 'height' specially for tables > >and textblocks: now, it is not possible anymore that the height of > >table or a textblock is less than the inherent height. This fixes > > > >- <http://forums.thinkbroadband.com> and > >- <https://linicks.net/AnAdIc/> (looks as with dillo 3.0.5). > > > >For tables, dillo behaves the same way as Firefox; for textblock not > >quite, but somewhat similar as dillo 3.0.5. This means that there is > >no regression, and that texblock heights may be worked on after the > >next release. Also very good in this case [1]! [1] http://www.btgpactual.mdgms.com/www/chile/resume.html -- Cheers Jorge.-

April 23, 2016

GROWS fixes

by nick＠linicks.net

Hi Seb, On 23/04/16 17:04, Sebastian Geerken wrote: > Hi! > > After the recent changes, dillo handles 'height' specially for tables > and textblocks: now, it is not possible anymore that the height of > table or a textblock is less than the inherent height. This fixes > > - <http://forums.thinkbroadband.com> and > - <https://linicks.net/AnAdIc/> (looks as with dillo 3.0.5). > > For tables, dillo behaves the same way as Firefox; for textblock not > quite, but somewhat similar as dillo 3.0.5. This means that there is > no regression, and that texblock heights may be worked on after the > next release. Brilliant job - thank you very much. Since I 'rediscovered Dillo' after 14 years or so, I am using it now more and more every day. So fast. I also wish more people would produce 'proper' web pages - Dillo is far the best on these - e.g. one game I play twice a day is the great 'scrabble challenge': http://ironphoenix.org/scrabble/ Just bloody perfect in Dillo! Again, many thanks, Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

April 23, 2016

GROWS fixes

by sgeerken＠dillo.org

Hi! After the recent changes, dillo handles 'height' specially for tables and textblocks: now, it is not possible anymore that the height of table or a textblock is less than the inherent height. This fixes - <http://forums.thinkbroadband.com> and - <https://linicks.net/AnAdIc/> (looks as with dillo 3.0.5). For tables, dillo behaves the same way as Firefox; for textblock not quite, but somewhat similar as dillo 3.0.5. This means that there is no regression, and that texblock heights may be worked on after the next release. Sebastian

April 23, 2016

Dillo_grows merged

by jcid＠dillo.org

On Mon, Apr 18, 2016 at 06:16:40PM +0200, Sebastian Geerken wrote: > Hi! > > The dillo_grows repository has just been merged into the main > repository at <http://hg.dillo.org/dillo>. > > Hopefully, this will mean that all these changes will soon make it > into a new release. My testing went great so far, so +1. Again, I'm very pleased to have dillo's speed back! 8-) -- Cheers Jorge.-

April 23, 2016