- Dillo-dev - lists.mailman3.com

should we have a dillo-announce list?

by eocene＠gmx.com

Seems like a release announcements list would be valuable...

Jan. 3, 2015

what's currently broken in dillo

by Johannes.Hofmann＠gmx.de

On Sat, Jan 03, 2015 at 01:13:11AM +0100, Sebastian Geerken wrote: > On Fr, Jan 02, 2015, Jorge Arellano Cid wrote: > > It's a bit sad to find time and again that 3.0.4 has better rendering > > than the new branch. (e.g. [1]) > > The new branch is still in development. > > I'm currently working on another page, which shows a similar behaviour > (table with too wide columns); in my case, the reason is a plain bug > which will be fixed soon. Hopefully, your case will be similar. > > There are some other issues: > > 2. What to do with badly designed pages, which are now less readabe > since dillo supports new CSS attribues? "adjust_min_width" is a > solution to one of those problems. > > 3. It may be that incomplete support (say, floats but no absolute > positions) may cause some problems. > > Anyway, I believe that most reports fall into the first category. We always had these issues since we started with CSS. Sometimes implementing a feature makes rendering worse instead of better on some pages. But Sebastian's most recent commits improved things a lot again. And you can always add "* {float: none !important}" to your ~/.dillo/style.css Cheers, Johannes

Jan. 3, 2015

what's currently broken in dillo

by sgeerken＠dillo.org

On Fr, Jan 02, 2015, Jorge Arellano Cid wrote: > It's a bit sad to find time and again that 3.0.4 has better rendering > than the new branch. (e.g. [1]) The new branch is still in development. I'm currently working on another page, which shows a similar behaviour (table with too wide columns); in my case, the reason is a plain bug which will be fixed soon. Hopefully, your case will be similar. There are some other issues: 2. What to do with badly designed pages, which are now less readabe since dillo supports new CSS attribues? "adjust_min_width" is a solution to one of those problems. 3. It may be that incomplete support (say, floats but no absolute positions) may cause some problems. Anyway, I believe that most reports fall into the first category. Sebastian

Jan. 3, 2015

what's currently broken in dillo

by jcid＠dillo.org

On Fri, Jan 02, 2015 at 07:32:52PM +0000, eocene wrote: > Sebastian wrote: > > Yes, I now see; I assume that you mean this: > > > > http://www.dillo.org/~sgeerken/attic/forecast.weather.gov_01.png > > > > I'll look at it. > > Yes, that. Thanks... I'm just using the new setting, and *anything* that helps to have better rendering is welcomed. It's a bit sad to find time and again that 3.0.4 has better rendering than the new branch. (e.g. [1]) OTOH, it looks like if dillo is the one to finally decide how to fit the layout and not the plethora of redundant & weird directives, our postmodern HTML pages have, it'll be much better for everybody. I mean, if the given directives pass our weirdness test, follow them, if not, use our criteria. May be adjustable too. e.g. 1: always follow dillo heuristics 2: when in shallow doubt, follow dillo heuristics 3: only if width exceeds viewport, follow dillo heuristics 4: only if the page is too large/weird, follow dillo heuristics. 5: always follow HTML/CSS/* directives. DISCLAIMER HINT: as stated before. In the long term past, similar schemes ended in just a simple "follow dillo's heuristics unless forced not to". [1] http://actualidad.rt.com/economia/161785-china-devastador-dolar-rublo-yuanes -- Cheers Jorge.-

Jan. 2, 2015

what's currently broken in dillo

by eocene＠gmx.com

Sebastian wrote: > Yes, I now see; I assume that you mean this: > > http://www.dillo.org/~sgeerken/attic/forecast.weather.gov_01.png > > I'll look at it. Yes, that. Thanks...

Jan. 2, 2015

what's currently broken in dillo

by sgeerken＠dillo.org

On Fr, Jan 02, 2015, eocene wrote: > Sebastian wrote: > > > > > - on some sites, the ending words of a line are missing. > > > > > > The forecasts on the US national weather service page do this for me. > > > See the Detailed Forecast section. > > > Example: http://forecast.weather.gov/MapClick.php?lat=40&lon=-90 > > > > I'm not sure, I cannot reproduce it now; but I've fixed a bug > > demonstrated in the attached test page. Element #b is 1000px wide, but > > its parent, #a, is set to 100%, which refers to the viewport width > > (more or less), which may be less than 1000px. Note also #c, which is > > broken at the viewport width. > > > > Without 'adjust_min_width' set, parts of #b are indeed clipped; when > > set to 'YES', the width of #a, and so the srollable area, are adjusted > > (but not the width of #c), so that you can scroll to the right to read > > the rest. > > > > Currently, 'adjust_min_width' is not set by default. Probably, it > > should be set, to avoid such cases. What do you think? > > If it keeps text from being clipped, it sounds good. It is now set by default. > The weather page still breaks for me. Had you been able to reproduce the > problem earlier? I just tried moving dillorc and domainrc without any > effect on it. Yes, I now see; I assume that you mean this: http://www.dillo.org/~sgeerken/attic/forecast.weather.gov_01.png I'll look at it. Sebastian

Jan. 2, 2015

what's currently broken in dillo

by eocene＠gmx.com

Sebastian wrote: > > > > - on some sites, the ending words of a line are missing. > > > > The forecasts on the US national weather service page do this for me. > > See the Detailed Forecast section. > > Example: http://forecast.weather.gov/MapClick.php?lat=40&lon=-90 > > I'm not sure, I cannot reproduce it now; but I've fixed a bug > demonstrated in the attached test page. Element #b is 1000px wide, but > its parent, #a, is set to 100%, which refers to the viewport width > (more or less), which may be less than 1000px. Note also #c, which is > broken at the viewport width. > > Without 'adjust_min_width' set, parts of #b are indeed clipped; when > set to 'YES', the width of #a, and so the srollable area, are adjusted > (but not the width of #c), so that you can scroll to the right to read > the rest. > > Currently, 'adjust_min_width' is not set by default. Probably, it > should be set, to avoid such cases. What do you think? If it keeps text from being clipped, it sounds good. The weather page still breaks for me. Had you been able to reproduce the problem earlier? I just tried moving dillorc and domainrc without any effect on it.

Jan. 2, 2015

what's currently broken in dillo

by jcid＠dillo.org

On Fri, Jan 02, 2015 at 06:13:38PM +0100, Sebastian Geerken wrote: > > > > - on some sites, the ending words of a line are missing. > > > > The forecasts on the US national weather service page do this for me. > > See the Detailed Forecast section. > > Example: http://forecast.weather.gov/MapClick.php?lat=40&lon=-90 > > I'm not sure, I cannot reproduce it now; but I've fixed a bug > demonstrated in the attached test page. Element #b is 1000px wide, but > its parent, #a, is set to 100%, which refers to the viewport width > (more or less), which may be less than 1000px. Note also #c, which is > broken at the viewport width. > > Without 'adjust_min_width' set, parts of #b are indeed clipped; when > set to 'YES', the width of #a, and so the srollable area, are adjusted > (but not the width of #c), so that you can scroll to the right to read > the rest. > > Currently, 'adjust_min_width' is not set by default. Probably, it > should be set, to avoid such cases. What do you think? Speaking from experience gained from having to handle HTML parsing errors, and table apportioning algorithms, with all the contradicting directives, overrides, etc. In the long run, having dillo decide the final values by adding a cleanup stage at some points, has emerged as the choice with better rendering. (e.g. w3c_plus_heuristics=YES, cleanup_at_{open, close}(), contrast_visited_color=YES, ... ;) -- Cheers Jorge.-

Jan. 2, 2015

what's currently broken in dillo

by sgeerken＠dillo.org

> > > - on some sites, the ending words of a line are missing. > > The forecasts on the US national weather service page do this for me. > See the Detailed Forecast section. > Example: http://forecast.weather.gov/MapClick.php?lat=40&lon=-90 I'm not sure, I cannot reproduce it now; but I've fixed a bug demonstrated in the attached test page. Element #b is 1000px wide, but its parent, #a, is set to 100%, which refers to the viewport width (more or less), which may be less than 1000px. Note also #c, which is broken at the viewport width. Without 'adjust_min_width' set, parts of #b are indeed clipped; when set to 'YES', the width of #a, and so the srollable area, are adjusted (but not the width of #c), so that you can scroll to the right to read the rest. Currently, 'adjust_min_width' is not set by default. Probably, it should be set, to avoid such cases. What do you think? Sebastian

Jan. 2, 2015

what's currently broken in dillo

by eocene＠gmx.com

Sebastian wrote: > On Sun, Dec 28, 2014, eocene wrote: > > Sebastian wrote: > > > On Mi, Dez 24, 2014, eocene wrote: > > > > - on some sites, rendering never stops as the horizontal scrollbar shows the > > > > page growing wider and wider. > > > > arstechnica.com does this like 95% of the time (I think deterministically -- > > like you can catch them at a time when their html is such that it doesn't > > show the problem, but it normally does.) > > This seems fixed now. Great :)

Jan. 2, 2015