Changes between Initial Version and Version 1 of Ticket #16482, comment 4


Ignore:
Timestamp:
Dec 17, 2012, 9:55:30 PM (7 years ago)
Author:
bill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16482, comment 4

    initial v1  
    1 Hmm, placeAt() isn't documented to be able to work on a !DocumentFragment.  The API doc says it takes a Widget, DOMNode, or id of widget or DOMNode.    I guess you are saying you want _WidgetBase.placeAt(docFrag) it to call through to domConstruct.place(), although that's also not documented to work with a !DocumentFragment.
     1Hmm, placeAt() isn't documented to be able to work on a !DocumentFragment.  The API doc says it takes a Widget, DOMNode, or id of widget or DOMNode.    I guess you are saying you want _WidgetBase.placeAt(docFrag) it to call through to domConstruct.place(), but domConstruct.place() is also not documented to work with a !DocumentFragment.
    22
    33> This will fail because reference.tagName is checked in placeAt which causes refWidget to be set to the document fragment.