Changes between Initial Version and Version 1 of Ticket #17132, comment 3


Ignore:
Timestamp:
May 13, 2013, 12:07:19 AM (8 years ago)
Author:
bill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17132, comment 3

    initial v1  
    11OK... well your patch will certainly fix the exception in that case.
    22
    3 Really though if the widget is destroyed with destroy(true), the _cssState flags from children should be removed.   Otherwise you'll have problems in a case of nested widgets:
     3Really though if the widget is destroyed with destroy(true), the _cssState properties on its DOMNode and its descendant DOMNodes should be removed.   Otherwise you'll have problems in the case of nested widgets:
    44
    55{{{
     
    99}}}
    1010
    11 If you call inner.destroy(true), then a mouse over nodeWithCssStateSet will send the notification to outer, specifically calling outer._subnodeCssMouseEvent().   I guess that would wouldn't cause an exception but technically it's not the correct behavior.
     11If you call inner.destroy(true), then a mouse over nodeWithCssStateSet will send the notification to outer, specifically calling outer._subnodeCssMouseEvent().   I guess that wouldn't cause an exception but technically it's not the correct behavior.
    1212
    1313For 2.0 though I'd like to get rid of _cssState property either altogether, or at least on widget subnodes, so the simple solution to avoid the exception seems fine for now.