In textareas (multiline form input), say for example: http://translate.google.ca/translate_t ... if I first enter the following line into the textarea: yo soy anarco-capitalista ... and after submitting it, I edit it (the previous contents are retained -- although I suspect internally there might be something broken -- not sure where it breaks exactly.), by inserting a newline at the very beginning (pressing enter), then backspacing (removing the newline) to make it appear exactly the same, then resubmitting the form, strange stuff happens. (I remember earlier posting experiences some of my lines getting duplicated, and other strange stuff. I think it only happens when I edit stuff at the beginning.)
Dennis wrote:
In textareas (multiline form input), say for example:
http://translate.google.ca/translate_t
... if I first enter the following line into the textarea:
yo soy anarco-capitalista
... and after submitting it, I edit it (the previous contents are retained -- although I suspect internally there might be something broken -- not sure where it breaks exactly.), by inserting a newline at the very beginning (pressing enter), then backspacing (removing the newline) to make it appear exactly the same, then resubmitting the form, strange stuff happens.
(I remember earlier posting experiences some of my lines getting duplicated, and other strange stuff. I think it only happens when I edit stuff at the beginning.)
You have found a FLTK bug. I think in the beginning of TextBuffer::text(), where it goes if (!gapstart_ && length_) { buf_[length_+gapend_] = 0; return buf_+gapstart_; } they want if (!gapstart_ && length_) { buf_[length_+gapend_] = 0; return buf_+gapend_; }
I wrote:
Dennis wrote:
In textareas (multiline form input), say for example:
http://translate.google.ca/translate_t
... if I first enter the following line into the textarea:
yo soy anarco-capitalista
... and after submitting it, I edit it (the previous contents are retained -- although I suspect internally there might be something broken -- not sure where it breaks exactly.), by inserting a newline at the very beginning (pressing enter), then backspacing (removing the newline) to make it appear exactly the same, then resubmitting the form, strange stuff happens.
(I remember earlier posting experiences some of my lines getting duplicated, and other strange stuff. I think it only happens when I edit stuff at the beginning.)
You have found a FLTK bug.
I think in the beginning of TextBuffer::text(), where it goes
if (!gapstart_ && length_) { buf_[length_+gapend_] = 0; return buf_+gapstart_; }
they want
if (!gapstart_ && length_) { buf_[length_+gapend_] = 0; return buf_+gapend_; }
The new FLTK2 weekly snapshot has the fix.
On Sat, 10 Oct 2009 00:44:53 +0000, corvid wrote:
I wrote:
Dennis wrote:
In textareas (multiline form input), say for example:
http://translate.google.ca/translate_t
... if I first enter the following line into the textarea:
yo soy anarco-capitalista
... and after submitting it, I edit it (the previous contents are retained -- although I suspect internally there might be something broken -- not sure where it breaks exactly.), by inserting a newline at the very beginning (pressing enter), then backspacing (removing the newline) to make it appear exactly the same, then resubmitting the form, strange stuff happens.
(I remember earlier posting experiences some of my lines getting duplicated, and other strange stuff. I think it only happens when I edit stuff at the beginning.)
You have found a FLTK bug.
I think in the beginning of TextBuffer::text(), where it goes
if (!gapstart_ && length_) { buf_[length_+gapend_] = 0; return buf_+gapstart_; }
they want
if (!gapstart_ && length_) { buf_[length_+gapend_] = 0; return buf_+gapend_; }
The new FLTK2 weekly snapshot has the fix.
Thank you!
participants (2)
-
corvid＠lavabit.com -
dennisn＠dennisn.dyndns.org