159979 - textarea wrapping controls dont work with javascript

Status: RESOLVED FIXED

(Core :: Layout: Form Controls, defect, P3)

Description

[Zurk]

From Bugzilla Helper:
User-Agent: Mozilla/4.08 [en] (WinNT; I ;Nav)
BuildID:    20020530

Javascript control to switch wrapping to physical, soft, hard, virtual or off 
does not work in mozilla.
http://bugzilla.mozilla.org/attachment.cgi?id=93042&action=view
for a test case.

Please assign to kin.
Reproducible: Always
Steps to Reproduce:
1.load page
2.select menu.
3.

Actual Results:  doesnt work.


Expected Results:  should work.

Comment 1

[rods (gone)]

-->

Comment 2

[Brad K.]

Attachment: Access TEXTAREA values from Javascript

This fragment uses two methods to access TEXTAREA contents in a form, using the
onCLick event.

The first textarea uses this.innerText to display the contents in an alert
popup, and works in IE6, but the alert box shows 'undefined' in NS6.2 and Moz
1.1 build 2002083008

The second box uses this.getAttribute("value"), and works in IE6 and NS 6.2,
but the alert box is empty in Moz 1.1 with no text or warning.	Note that Moz
1.1 build 20020830008 incorrectly disables text wrapping for the 'wrap=virtual'
text the same as the 'WRAP=OFF' text.

Comment 3

[kinmoz]

Brad, you can retrieve the value of the textarea by using |this.value| which
according to the DOM spec is how you can retrieve the text from a textarea. Note
that there is no "value=" attribute on your <textarea>, so that's probably why
you are getting nothing back when you call getAttribute().

Aside from dynamically changing the wrap attribute's value being broken, which
is what this bug is about, we are also aware that we currently don't break in
the middle of words that are wider than the textarea's viewport to force a wrap.
That's probably what you are seeing. I've got a bug about that somewhere.

Comment 4

[Jason]

Just like to "bump" this bug. Still not fixed after over a year.

Comment 5

[Martin Packer]

Could someone test if the fix for https://bugzilla.mozilla.org/show_bug.cgi?id=41464 also fixes this one. (As the comments therein suggest it might.)

Comment 6

[Boris Zbarsky [:bzbarsky]]

Yep, that patch fixed this.  And the tests there test it.