[Webkit-unassigned] [Bug 6893] REGRESSION: Major bug with TinyMCE, no value submitted from textarea

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=6893


justin.garcia at apple.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |darin at apple.com,
                   |                            |adele at apple.com




------- Comment #3 from justin.garcia at apple.com  2006-01-30 19:25 -------
This regression was caused by the changes for
<http://bugzilla.opendarwin.org/show_bug.cgi?id=3401>.  I have a question about
textareas and \r\ns.  
(1) We turn \r\ns into \ns when tokenizing, so that any \r\ns that are inside
<textarea></textarea>s in the source are turned into \ns, are sent into the
renderer as \n and are returned by .value and .defaultValue as \n.  
(2) When someone sets .value, we send \r\ns into the renderer, but translate
them into \ns in -[KWQTextArea text], so that they are returned as \n when
calling .value (That is, unless .value is called on a textarea with no
renderer, in which case we incorrectly return .defaultValue instead of .value,
which is this bug).
(3) When someone sets .defaultValue, we put \r\n into the DOM, send \r\n to the
renderer, but _do not_ translate them back when asked for .defaultValue.
(4) -[KWQTextArea setSelectedRange] and -[KWQTextArea selectedRange] work
around (2)

My question is, why put \r\ns into the renderer?  What do you think about
converting \r\ns into \ns in setDefaultValue and setValue?  It seems to me that
doing so would make the strings returned by .value and .defaultValue
consistent, and would eliminate the need for the workarounds in
setSelectedRange and selectedRange (4).


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.