On Sat, May 03, 2014 at 01:32:35PM +0200, Sebastian Geerken wrote:
On Do, Mai 01, 2014, Johannes Hofmann wrote:
On Thu, May 01, 2014 at 11:02:54PM +0200, Sebastian Geerken wrote:
On Thu, May 01, 2014, Sebastian Geerken wrote:
On Do, Mai 01, 2014, Jorge Arellano Cid wrote:
Good!
It works OK now.
This one [2] still hogs the CPU between two alternate layouts. There's no need to enable images, just the main page and remote CSS will do.
I cannot reproduce this: with revision 3637, the page looks fine, without flickering or CPU hogging. (Everything enabled, but turning off images has the same effect.)
Updates:
1. I can neither reproduce it with standard configuration ("mv .dillo .dillo_").
I still get something like that with http://slashdot.org
This is working now. Unfortunately, the text is much too wide, which is due to some CSS definitions "text-indent: 9999px".i (I don't know whether this is a trick only working in some browsers, or whether dillo is incomplete and should actually ignore this.) If you put this in your ~/.dillo/style.css, slashdot becomes readable again:
---------------------------------------------------------------------- .spinner .tag-server-busy.spinner, .fhitem-editor .tag-server-busy, article footer .tag-server-busy, #edit-busy.busy.spinner, .synd .rss, .synd .tw, .synd .fb, .synd .gp, ui-icon.pref a, .ui-icon.edit a, .ui-icon.rss a, #user_bio .prefs a, #commentwrap .ui-icon.search { text-indent:0px !important; } ----------------------------------------------------------------------
Cool, thank you! Regarding this "text-indent: 9999px", I've seen this a couple of time and it seems to be a common trick [1]. Cheers, Johannes [1] http://luigimontanez.com/2010/stop-using-text-indent-css-trick/