Re: New textareas and text inputs

On Wed, 13 Feb 2013 21:16:45 +0000 (GMT), Michael Drake wrote:

> > I'm getting strange effects on the last line of multi-line areas on
> > occasion (maybe when the last line is the first line of a line which
> > extends onto the next line? - if that makes sense!), but I haven't been
> > able to reproduce it on demand.
>
> I've not seen that. Do you mean a textarea line which is soft-wrapped to a
> line out of sight below the visible display? I've not seen that here.

Yes.

> > What happens is that NetSurf displays the correct thing, but the caret
> > stops before the end of the line, as if something different is there.
>
> So if you move the caret with cursor-right key, it doesn't reach the end
> of the displayed text?
>
> The last character on a soft-wrapped line is a space, but you can't put
> the caret to the right of it, a caret after the space is on the start of
> the next line.

It gets as far as the length of the line below it, it looks like it is
confused as to which line it is actually on. Pressing enter appears
to act as if it is on the line below too (and then refreshes it and
everything works as it should). If I can get it to do it again, I'll
save a copy of my text.

> > I'm also getting a serious memory leak during usage, but I'm not sure
> > if that is related to the new textareas, JavaScript or something else
> > - all I know is that it appears to have started within the last week
> > (and it isn't my box redraw queue - I've checked that), and typing
> > things into textareas eventually grinds to a halt (due to lack of
> > memory - although it might not be the typing into textareas which is
> > the cause)
>
> This is concerning. I'll have a look.

I start with about 400MB, it disappears to nothing during use, and
when I quit NetSurf it only frees up less than 100MB. It looks like
something isn't getting freed.

I've just been playing around with it trying to reproduce the "last
line" bug (I couldn't), and I'm down to 150MB - after quitting NetSurf
- from a starting point of 400MB. That's with JavaScript disabled, so
we can eliminate that.

Chris