Re: white-space patch

Jorge Arellano Cid <[email protected]>
Newsgroups gmane.comp.web.dillo.devel
Message-ID <[email protected]>
On Sat, Oct 01, 2011 at 04:45:52PM +0000, corvid wrote:
> Jorge wrote:
> > On Sat, Oct 01, 2011 at 11:03:18AM -0300, Jorge Arellano Cid wrote:
> > > On Fri, Sep 30, 2011 at 08:54:39AM +0200, Johannes Hofmann wrote:
> > > > On Wed, Sep 28, 2011 at 05:49:10PM -0300, Jorge Arellano Cid wrote:
> > 
> > > > >   [...]
> > > > >   Please explain the non-deterministical behaviour at google.
> > > > 
> > > > If I search for e.g. dillo on google, the first line (the link) of a
> > > > result entry is sometimes broken into two lines, sometimes not.
> > > 
> > >   Thanks for the explanation.
> > > 
> > >   After some time reviewing it and guessing, I succeeded to isolate
> > > a small testcase which I'm reviewing now.
> > 
> >   Sorry, it was not a reliable testcase...  :-P
> 
> I haven't looked into this, but do you suppose it could have to do with the
> part in html.cc that goes
> 
>       if (isspace(buf[buf_index])) {
>          /* whitespace: group all available whitespace */
>          while (++buf_index < bufsize && isspace(buf[buf_index])) ;
>          Html_process_space(html, buf + token_start, buf_index - token_start);
>          token_start = buf_index;
>       } ...
> 
> that is, sends off whatever it's accumulated at the end of a packet?

  Not sure, but I don't think so.

  Without  the  whitespace  patch, dillo also doesn't seem to get
right the available horizontal space for the link [1].

  To  me it looks related to the way ParMin propagates upwards in
a textblock, but I'm just starting to look into it.

  BTW, adding these lines to style.css helps to visualize it:

    table {border: 1px solid red !important}
    td {border: 1px solid green !important}
    div {border: 1px solid black !important}


  
[1] http://www.google.com/search?ie=UTF-8&oe=UTF-8&q=dillo

-- 
  Cheers
  Jorge.-
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.