Changes between Initial Version and Version 2 of Ticket #4251


Ignore:
Timestamp:
Aug 27, 2007, 12:57:27 PM (13 years ago)
Author:
bill
Comment:

Ah o.k., updating the bug description to be accurate. Yeah, it's only a problem for programmatically created nodes, but still bad.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4251

    • Property Summary changed from Textarea: won't initialize in dialog, hidden div, etc. (FF) to Textarea: programmatic creation fails (FF)
  • Ticket #4251 – Description

    initial v2  
    1 On FF, Textarea widget does sizing on initialization, which fails (it gets a size of 0).  Just try a testcase with a Textarea widget inside a hidden tab, or a dialog with style="display: none".
    2 
    3 Probably need to implement Textarea as a plain <textarea> node on FF.
    4 
    5 Alternate possibilities include:
    6  - detecting when a widget becomes visible/hidden due to a change in an ancestors' CSS (I don't think this is possible.)
    7  - stop using display:hidden in any of our widgets.  But that's a big change.
    8 
    9 See also #3980.
     1postCreate() of Textarea is being called before the domNode has been inserted into the document, causing the iframe to not have a contentWindow.  See attached testcase (press new message button)