Storage is too generic. What does it meant to clone it? If I have an element with an array stored on it, do we copy the array? Or do the two elements share it? What if a class is stored on the element, like Form.Validator. We can't just copy the object and expect it to work. What if a DOM element is stored? Do we clone it too?
On Thu, Jan 28, 2010 at 4:08 AM, Dimitar Christoff <[email protected]>wrote: > basically, cloning an element leaves behind events and storage. there's > a cloneEvents method but no cloneStorage. > > This is relatively easy the element storage runs inside of a closure, so > -core would need to be modified (I can't think of a way of accessing the > get function and .the storage object as is) > > do you think it's a feature worth including - i bumped into this problem > the other day? > > cheers > -- > Dimitar Christoff <[email protected]> - http://fragged.org/ > >
