Bug Tracker

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


Ignore:
Timestamp:
Nov 26, 2010, 3:17:23 PM (10 years ago)
Author:
addyosmani
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7639, comment 4

    initial v1  
    1 Our further discussions on this seem to indicate that there is a level of validity to it getting fixed. The regular DOM way of achieving the desired effect works and so it should work equally as well with jQuery.
     1Our further discussions on this seem to indicate that there is a level of validity to it getting fixed. Our group consensus is that at minimum, elements should not simply 'disappear' as per what was experienced with the original ticket.
    22
    3 Without digging too deeply into the code, we believe that the reason this issue is being caused is that we're internally pulling the element in a fragment and inserting obviously fails since it isn't there anymore and no longer has a parent.
     3Without digging too deeply into the code, we believe that the reason this issue is being caused is because we're internally pulling the element in a fragment and inserting obviously fails since it isn't there anymore and no longer has a parent.
    44
    55Our current concern is how costly it would be to do the required check across all manipulation methods - we don't *think* it would be too expensive, however we could be wrong. CC'ing John for his input too.