- Dillo-dev - lists.mailman3.com

clipping image inputs

by corvid＠lavabit.com

Johannes wrote: > On Wed, Mar 04, 2009 at 08:22:12PM +0000, corvid wrote: > > With > > > > <input type="image" name="name1" src="whatever" > > WIDTH="80" HEIGHT="14" > > alt="name1name1name1name1"> > > <input type="image" name="name2" src="whatever" > > width="9" height="14" > > alt="name2name2name2name2"> > > > > the long alt text doesn't clip. > > It looks like the embed knows that it's 80 pixels wide > > (at least the child widget area stuff in Textblock::drawLine > > seemed to have the right idea), > > but the image thinks it's 188 (in my case). > > Can you please test attached patch? Not sure if it covers all > related cases, but for me it fixes the above example. Seems to be working for me, too. Thanks...

March 5, 2009

allow_white_bg and contrast_visited_color

by Johannes.Hofmann＠gmx.de

Hi, as we seem to have agreed on using CSS for style customization intead of dillorc settings, I'm trying to get rid of these: link_color: visited_color: text_color: bg_color: force_my_colors: The same thing can more or less be expressed with a custom user stylesheet, so I want to remove them. The problem is non-HTML pages (plain). I would propose to simulate <body><pre> in this case and use the corresponding style. allow_white_bg: This can't be expressed with CSS. We could detect a white background in StyleEngine (like we detect font sizes smaller than font_min_size), but what color should we use instead in this case (note that it must be different enough from the text color)? contrast_visited_color: This one is hard. Consider we want to render a visited link. >From StyleEngine we get a background and a text color, but we don't know what the text color would have been if the link would not be visited. So we can't enforce a color that is different from that. Generally (and even more with CSS), background- and text-colors can change arbitrarily within a page. So there is not a background and a text color per page. standard_widget_colors: Not sure about this one. On the one hand I think that CSS support broke this. On the other hand CSS allows the page author to directly set colors of form widgets. corvid, can you please have a look? Cheers, Johannes

March 5, 2009

clipping image inputs

by Johannes.Hofmann＠gmx.de

On Wed, Mar 04, 2009 at 08:22:12PM +0000, corvid wrote: > With > > <input type="image" name="name1" src="whatever" > WIDTH="80" HEIGHT="14" > alt="name1name1name1name1"> > <input type="image" name="name2" src="whatever" > width="9" height="14" > alt="name2name2name2name2"> > > the long alt text doesn't clip. > It looks like the embed knows that it's 80 pixels wide > (at least the child widget area stuff in Textblock::drawLine > seemed to have the right idea), > but the image thinks it's 188 (in my case). Can you please test attached patch? Not sure if it covers all related cases, but for me it fixes the above example. Cheers, Johannes

March 5, 2009

RFC: Dillo presentation

by corvid＠lavabit.com

furaisanjin wrote: > 2009/3/5 Jorge Arellano Cid <jcid(a)dillo.org>: > > ? ?- Low bandwidth requirement (very important in rural areas) > > Is there any plan to limit simultaneous HTTP connections? If the page > contains lots of pictures, dillo generates simultaneous HTTP > connections to fetch them and those occupy certain amount of > bandwidth. Speaking of which, it would be nice to use Connection: Keep-Alive as part of this.

March 5, 2009

clipping image inputs

by Johannes.Hofmann＠gmx.de

On Thu, Mar 05, 2009 at 12:03:48AM +0000, corvid wrote: > Johannes wrote: > > On Wed, Mar 04, 2009 at 08:22:12PM +0000, corvid wrote: > > > With > > > > > > <input type="image" name="name1" src="whatever" > > > WIDTH="80" HEIGHT="14" > > > alt="name1name1name1name1"> > > > <input type="image" name="name2" src="whatever" > > > width="9" height="14" > > > alt="name2name2name2name2"> > > > > > > the long alt text doesn't clip. > > > It looks like the embed knows that it's 80 pixels wide > > > (at least the child widget area stuff in Textblock::drawLine > > > seemed to have the right idea), > > > but the image thinks it's 188 (in my case). > > > > > > > > > PS I have "white-space: nowrap" pretty much working, > > > but I don't know what I'm doing in Textblock very well, > > > so it's definitely not going into this release. > > > > Can you explain the issue your are working on? At least > > > > <div style="white-space: nowrap">foo bar foo bar foo bar</div> > > > > seems to work already (the line is not wrapped). > > First I noticed that the boxes at the bottoms of the pages about > web browser stuff in en.wikipedia weren't wrapping (including > Dillo's page) because they go <..nowrap>...</span> <span..nowrap>...</span> > and it wasn't taking spaceStyle->whiteSpace into account. > Not handling its own wikipedia page well is sort of unfortunate. > > and then I found that if you have a line that goes: > some normal text <span ...nowrap>really really long stretch of nowrap</span>, > it wouldn't break before the span. I see.

March 5, 2009

improving CSS performance

by Johannes.Hofmann＠gmx.de

Hi, I just commited http://hg.dillo.org/dillo?cs=11c6f887d649 which improves CSS performance by avoiding unnecessary style computations. Please give it a thorough testing. Cheers, Johannes

March 5, 2009

RFC: Dillo presentation

by furaisanjin＠gmail.com

Hi, 2009/3/5 Jorge Arellano Cid <jcid(a)dillo.org>: > ? ?- Low bandwidth requirement (very important in rural areas) Is there any plan to limit simultaneous HTTP connections? If the page contains lots of pictures, dillo generates simultaneous HTTP connections to fetch them and those occupy certain amount of bandwidth. Regards, furaisanjin

March 5, 2009

RFC: Dillo presentation

by onepoint＠starurchin.org

Many thanks, Jorge! Updated checklist attached. Regards, Jeremy Henty

March 5, 2009

clipping image inputs

by corvid＠lavabit.com

Johannes wrote: > On Wed, Mar 04, 2009 at 08:22:12PM +0000, corvid wrote: > > With > > > > <input type="image" name="name1" src="whatever" > > WIDTH="80" HEIGHT="14" > > alt="name1name1name1name1"> > > <input type="image" name="name2" src="whatever" > > width="9" height="14" > > alt="name2name2name2name2"> > > > > the long alt text doesn't clip. > > It looks like the embed knows that it's 80 pixels wide > > (at least the child widget area stuff in Textblock::drawLine > > seemed to have the right idea), > > but the image thinks it's 188 (in my case). > > > > > > PS I have "white-space: nowrap" pretty much working, > > but I don't know what I'm doing in Textblock very well, > > so it's definitely not going into this release. > > Can you explain the issue your are working on? At least > > <div style="white-space: nowrap">foo bar foo bar foo bar</div> > > seems to work already (the line is not wrapped). First I noticed that the boxes at the bottoms of the pages about web browser stuff in en.wikipedia weren't wrapping (including Dillo's page) because they go <..nowrap>...</span> <span..nowrap>...</span> and it wasn't taking spaceStyle->whiteSpace into account. Not handling its own wikipedia page well is sort of unfortunate. and then I found that if you have a line that goes: some normal text <span ...nowrap>really really long stretch of nowrap</span>, it wouldn't break before the span. There may be other cases as well.

March 5, 2009

clipping image inputs

by Johannes.Hofmann＠gmx.de

On Wed, Mar 04, 2009 at 08:22:12PM +0000, corvid wrote: > With > > <input type="image" name="name1" src="whatever" > WIDTH="80" HEIGHT="14" > alt="name1name1name1name1"> > <input type="image" name="name2" src="whatever" > width="9" height="14" > alt="name2name2name2name2"> > > the long alt text doesn't clip. > It looks like the embed knows that it's 80 pixels wide > (at least the child widget area stuff in Textblock::drawLine > seemed to have the right idea), > but the image thinks it's 188 (in my case). > > > PS I have "white-space: nowrap" pretty much working, > but I don't know what I'm doing in Textblock very well, > so it's definitely not going into this release. Can you explain the issue your are working on? At least <div style="white-space: nowrap">foo bar foo bar foo bar</div> seems to work already (the line is not wrapped). Cheers, Johannes

March 4, 2009