November 2009 - Dillo-dev - lists.mailman3.com

weird font

by corvid＠lavabit.com

Johannes wrote: > On Wed, Nov 11, 2009 at 12:35:49PM -0300, Jorge Arellano Cid wrote: > > On Tue, Nov 10, 2009 at 11:06:30PM +0100, Johannes Hofmann wrote: > > > Hi Jorge, > > > > > > On Tue, Nov 10, 2009 at 06:46:45PM -0300, Jorge Arellano Cid wrote: > > > > Hi, > > > > > > > > On some sites I get weird fonts. Today I got to isolate the > > > > problem. See attached file. Here it displays like this: > > > > > > > > http://www.dillo.org/test/xmp2.png > > > > > > > > The embedded CSS says: > > > > > > > > pre { font-family: MS Courier New, Courier, monospace; } > > > > > > > > If I remove "MS Courier New", it works OK. > > > > Any clues? > > > > > > There are multiple issues with font selection: > > > > > > * The CSS parser only returns the part until the first blank > > > ('MS' in this case). > > > * StyleEngine currently does not handle comma separated font name > > > lists (see \todo comment). > > > * ::fltk::font(name, fa); in fltkplatform.cc does not offer a way to > > > determine whether a font with that name actually exists on the > > > system. Instead if no exact match can be found, it guesses a > > > replacement font. This makes it impossible for dillo to choose the > > > right one from a given list. > > > > > > In your specific case, fltk gets the string 'MS' and on your system > > > it seems to find some funny font that has a similar name. > > > > Thanks for the detailed explanation. > > I just committed a fix for the first two issues. This should also > fix your problem. > It still does not test all font names in the list as I don't know > how to do that with fltk2, but it's a step in the right direction. I was also sure that fltk would choose a default font for us, but I was just gdbing FltkFont::FltkFont(), and ::fltk::font() did come back NULL when given a font name that it didn't recognize.

Nov. 15, 2009

auth segfault (Re: [Dillo-dev] Q: why do we defer loading linked stylesheets?)

by corvid＠lavabit.com

Jeremy wrote: > On Sat, Nov 14, 2009 at 03:42:00PM +0000, corvid wrote: > > > Speaking of repush, I see that there's another bug about auth and > > segfaults in the bug tracker. > > Which one? 928

Nov. 15, 2009

Q: why do we defer loading linked stylesheets?

by onepoint＠starurchin.org

On Sat, Nov 14, 2009 at 03:42:00PM +0000, corvid wrote: > Speaking of repush, I see that there's another bug about auth and > segfaults in the bug tracker. Which one? Regards, Jeremy Henty

Nov. 15, 2009

weird font

by Johannes.Hofmann＠gmx.de

On Wed, Nov 11, 2009 at 12:35:49PM -0300, Jorge Arellano Cid wrote: > On Tue, Nov 10, 2009 at 11:06:30PM +0100, Johannes Hofmann wrote: > > Hi Jorge, > > > > On Tue, Nov 10, 2009 at 06:46:45PM -0300, Jorge Arellano Cid wrote: > > > Hi, > > > > > > On some sites I get weird fonts. Today I got to isolate the > > > problem. See attached file. Here it displays like this: > > > > > > http://www.dillo.org/test/xmp2.png > > > > > > The embedded CSS says: > > > > > > pre { font-family: MS Courier New, Courier, monospace; } > > > > > > If I remove "MS Courier New", it works OK. > > > Any clues? > > > > There are multiple issues with font selection: > > > > * The CSS parser only returns the part until the first blank > > ('MS' in this case). > > * StyleEngine currently does not handle comma separated font name > > lists (see \todo comment). > > * ::fltk::font(name, fa); in fltkplatform.cc does not offer a way to > > determine whether a font with that name actually exists on the > > system. Instead if no exact match can be found, it guesses a > > replacement font. This makes it impossible for dillo to choose the > > right one from a given list. > > > > In your specific case, fltk gets the string 'MS' and on your system > > it seems to find some funny font that has a similar name. > > Thanks for the detailed explanation. I just committed a fix for the first two issues. This should also fix your problem. It still does not test all font names in the list as I don't know how to do that with fltk2, but it's a step in the right direction. Cheers, Johannes

Nov. 15, 2009

Q: why do we defer loading linked stylesheets?

by corvid＠lavabit.com

Johannes wrote: > On Sat, Nov 14, 2009 at 10:16:07AM +0000, Jeremy Henty wrote: > > On Fri, Nov 13, 2009 at 08:05:05AM +0000, corvid wrote: > > > Jeremy wrote: > > > > Why do we defer loading the CSS stylesheets named in <link> > > > > elements until the <head> element is closed? In html.cc, > > > > Html_tag_close_head() has the comment "charset is already set, > > > > load remote stylesheets now", but I don't understand the > > > > significance of the charset. > > > > > > > > [...] > > > > > > It looks like it dates to > > > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-February/005870.html > > > > Yuk! So what should we do if the <head> includes a <style> element > > that @imports a style sheet? Defer loading that stylesheet until the > > end of the <head>? Maybe defer parsing the entire <style> element? > > Shouldn't we treat all the style information in the same way? It > > seems to me that currently we don't. (Mind you, I'm not familiar with > > these charset and reepush issues so I'm probably missing something.) > > I don't remember all the details, but the basic idea is to defer the > repush (not the loading), so we repush - and as a consequence > redraw - the page just once. > So in your example with an @import directive in the <style> element > body, we would parse it if it is readily available in the cache. But > if not, we continue rendering without it. Then, once <head> is > closed and all requested style sheets are in cache, we repush the > page and restart parsing from start. > There is still a chance that during that repush we find a new > style sheet to be loaded due to a @import in one of the style sheets > we had not examined yet. That seems to be an inherent problem of the > @import thing in general. Speaking of repush, I see that there's another bug about auth and segfaults in the bug tracker. (At least the Tim crash had to do with repush, as I recall.)

Nov. 14, 2009

Q: why do we defer loading linked stylesheets?

by Johannes.Hofmann＠gmx.de

On Sat, Nov 14, 2009 at 10:16:07AM +0000, Jeremy Henty wrote: > On Fri, Nov 13, 2009 at 08:05:05AM +0000, corvid wrote: > > Jeremy wrote: > > > Why do we defer loading the CSS stylesheets named in <link> > > > elements until the <head> element is closed? In html.cc, > > > Html_tag_close_head() has the comment "charset is already set, > > > load remote stylesheets now", but I don't understand the > > > significance of the charset. > > > > > > [...] > > > > It looks like it dates to > > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-February/005870.html > > Yuk! So what should we do if the <head> includes a <style> element > that @imports a style sheet? Defer loading that stylesheet until the > end of the <head>? Maybe defer parsing the entire <style> element? > Shouldn't we treat all the style information in the same way? It > seems to me that currently we don't. (Mind you, I'm not familiar with > these charset and reepush issues so I'm probably missing something.) I don't remember all the details, but the basic idea is to defer the repush (not the loading), so we repush - and as a consequence redraw - the page just once. So in your example with an @import directive in the <style> element body, we would parse it if it is readily available in the cache. But if not, we continue rendering without it. Then, once <head> is closed and all requested style sheets are in cache, we repush the page and restart parsing from start. There is still a chance that during that repush we find a new style sheet to be loaded due to a @import in one of the style sheets we had not examined yet. That seems to be an inherent problem of the @import thing in general. Cheers, Johannes

Nov. 14, 2009

Q: why do we defer loading linked stylesheets?

by onepoint＠starurchin.org

On Fri, Nov 13, 2009 at 08:05:05AM +0000, corvid wrote: > Jeremy wrote: > > Why do we defer loading the CSS stylesheets named in <link> > > elements until the <head> element is closed? In html.cc, > > Html_tag_close_head() has the comment "charset is already set, > > load remote stylesheets now", but I don't understand the > > significance of the charset. > > > > [...] > > It looks like it dates to > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-February/005870.html Yuk! So what should we do if the <head> includes a <style> element that @imports a style sheet? Defer loading that stylesheet until the end of the <head>? Maybe defer parsing the entire <style> element? Shouldn't we treat all the style information in the same way? It seems to me that currently we don't. (Mind you, I'm not familiar with these charset and reepush issues so I'm probably missing something.) Regards, Jeremy Henty

Nov. 14, 2009

Q: why do we defer loading linked stylesheets?

by corvid＠lavabit.com

Jeremy wrote: > Why do we defer loading the CSS stylesheets named in <link> elements > until the <head> element is closed? In html.cc, Html_tag_close_head() > has the comment "charset is already set, load remote stylesheets now", > but I don't understand the significance of the charset. > > I am asking because I'd like to patch Dillo to add @import-ed > stylesheets to the browser window popup menu, just as it already does > for <link>-ed stylesheets. At the moment this causes all sorts of > code branches (is the @import in a <link>-ed file or an embedded > <style>, if the latter, is it in the <head> or not). It would be much > simpler to just immediately load every style file at the same time as > it is added to html->ccsUrls , but that would change the behaviour to > load <link>-ed styles immediately instead of at the end of the <head> > element. Would that break anything? It looks like it dates to http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-February/005870.html

Nov. 13, 2009

Q: why do we defer loading linked stylesheets?

by onepoint＠starurchin.org

Why do we defer loading the CSS stylesheets named in <link> elements until the <head> element is closed? In html.cc, Html_tag_close_head() has the comment "charset is already set, load remote stylesheets now", but I don't understand the significance of the charset. I am asking because I'd like to patch Dillo to add @import-ed stylesheets to the browser window popup menu, just as it already does for <link>-ed stylesheets. At the moment this causes all sorts of code branches (is the @import in a <link>-ed file or an embedded <style>, if the latter, is it in the <head> or not). It would be much simpler to just immediately load every style file at the same time as it is added to html->ccsUrls , but that would change the behaviour to load <link>-ed styles immediately instead of at the end of the <head> element. Would that break anything? Regards, Jeremy Henty

Nov. 13, 2009

EAGAIN loop in IO_read

by jcid＠dillo.org

On Thu, Nov 12, 2009 at 09:01:03PM +0900, furaisanjin wrote: > This misleads, so I clarify. > > 2009/11/12 furaisanjin <furaisanjin(a)gmail.com>: > > > I have no idea but the problem did happen in one hour but now it's > > very difficult to make it happen. > > I haven't seen it since I applied the patch. Thanks, it's good to hear that! ;) -- Cheers Jorge.-

Nov. 12, 2009