- Dillo-dev - lists.mailman3.com

New design of tag nesting cleanup within the parser.

by jcid＠dillo.org

On Wed, Jun 22, 2016 at 08:46:28PM +0000, eocene wrote: > Jorge wrote: > > Yes, "must be closed" is the intended meaning. > > > > Is there a way to have the _same_ message in a softer tone? > > Umm...in ordinary spoken English, we'd be more likely to say > "has to be closed", but I might be missing what you're getting at. I like it! I just don't want the bug meter to sound harsh or pedantic. This phrase sounds well to me: (*advice*) " has to be closed before </td>" // *advice* instead of: " must be closed before </td>" // *reproach* If that's the correct interpretation of meaning, I'd prefer to use the "has to be closed" expression. -- Cheers Jorge.-

June 23, 2016

valgrind errors

by eocene＠gmx.com

I wrote: > Was just having a look at the valgrind errors, and I think the > main one is in textblock.cc: > > int leftBorder = boxOffsetX () + leftInnerPadding > + (lines->size () == 0 ? line1OffsetEff : 0); > > leftBorder being set to line1OffsetEff when line1OffsetEff > has not been initialized. I should have said 'making use of the value of line1OffsetEff'. I wasn't paying any attention to the specifics of the calculation because textblock has changed a lot since I worked on it...

June 22, 2016

valgrind errors

by eocene＠gmx.com

Another one is containerAllocationState not getting initialized in OOFPositionedMgr.

June 22, 2016

valgrind errors

by eocene＠gmx.com

Was just having a look at the valgrind errors, and I think the main one is in textblock.cc: int leftBorder = boxOffsetX () + leftInnerPadding + (lines->size () == 0 ? line1OffsetEff : 0); leftBorder being set to line1OffsetEff when line1OffsetEff has not been initialized.

June 22, 2016

New design of tag nesting cleanup within the parser.

by eocene＠gmx.com

Jorge wrote: > Yes, "must be closed" is the intended meaning. > > Is there a way to have the _same_ message in a softer tone? Umm...in ordinary spoken English, we'd be more likely to say "has to be closed", but I might be missing what you're getting at.

June 22, 2016

New design of tag nesting cleanup within the parser.

by jcid＠dillo.org

Hi, On Wed, Jun 22, 2016 at 05:18:12PM +0000, eocene wrote: > Jorge wrote: > > Please check the comments, then browse your regular sites and give it > > a test drive, then send some feedback. Oh, I meant the comments in hg! :-) Anyway checking the bug meter's messages doesn't hurt. > A fltk.org page gave the warning > "... must have been closed before </td>..." > and it wasn't clear what that meant. > > The src has > <td>some text</td> > > and in that case " must be closed before </td>" sounds right > to me. Oh, I didn't know until now that the phrase "must have been" can have two meanings in english. Yes, "must be closed" is the intended meaning. Is there a way to have the _same_ message in a softer tone? -- Cheers Jorge.-

June 22, 2016

New design of tag nesting cleanup within the parser.

by jcid＠dillo.org

On Wed, Jun 22, 2016 at 02:18:00PM +0000, eocene wrote: > Jorge wrote: > > Please check the comments, then browse your regular sites and give it > > a test drive, then send some feedback. > > The links to articles on arstechnica.com aren't working for me today. > The bug meter has lots of "<a> can't contain <figure>". Yes, this is the new HTML5's "transparent" mode. A is a transparent container, which is not yet handled by dillo. Let me think it a bit... -- Cheers Jorge.-

June 22, 2016

New design of tag nesting cleanup within the parser.

by eocene＠gmx.com

Jorge wrote: > Please check the comments, then browse your regular sites and give it > a test drive, then send some feedback. A fltk.org page gave the warning "... must have been closed before </td>..." and it wasn't clear what that meant. The src has <td>some text</td> and in that case " must be closed before </td>" sounds right to me.

June 22, 2016

New design of tag nesting cleanup within the parser.

by nick＠linicks.net

On Wed, 22 Jun 2016 14:18:00 +0000 eocene <eocene at gmx.com> wrote: > Jorge wrote: > > Please check the comments, then browse your regular sites and give > > it a test drive, then send some feedback. > > The links to articles on arstechnica.com aren't working for me today. > The bug meter has lots of "<a> can't contain <figure>". > /lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev Yes, same type of errors/no link works on the BBC news site: http://www.bbc.co.uk/news Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

June 22, 2016

New design of tag nesting cleanup within the parser.

by eocene＠gmx.com

Jorge wrote: > Please check the comments, then browse your regular sites and give it > a test drive, then send some feedback. The links to articles on arstechnica.com aren't working for me today. The bug meter has lots of "<a> can't contain <figure>".

June 22, 2016