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

"Sebastian Geerken" <[email protected]> 24 Apr 2016 13:24:35 +0200

Newsgroups	gmane.comp.web.dillo.devel
Message-ID	<[email protected]>

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

_______________________________________________
Dillo-dev mailing list
[email protected]
http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev

signature.asc (application/pgp-signature, 473 B)