Yes as indicated, those portions of code are used to detect
"containment of fragment objects" (not about position changes). That
is leading to this bug. The fragment object boundaries automatically
get removed later in subsequent editing and there is no need to tweak
delete for such objects using containment detection.
I have indicated the same in comments.
thanks for checking the patch.
On Mon, Apr 29, 2013 at 10:20 PM, joe joe <joegsoc2013@gmail.com> wrote:
> I saw your patch just remove most of code about position changes.
>
>
> Joe
>
> On Mon, Apr 29, 2013 at 2:55 AM, Vidh <vidhu2366@gmail.com> wrote:
>> Hi,
>>
>> I worked on this bug:
>> http://bugzilla.abisource.com/show_bug.cgi?id=12986
>>
>> I have uploaded the fix and also attached it with this mail.
>> Let me know how it looks!
>>
>> thanks!
>>
>> --
>> Vidhoon Viswanathan
>> +91 7760711773
-- Vidhoon Viswanathan +91 7760711773Received on Mon Apr 29 19:05:26 2013
This archive was generated by hypermail 2.1.8 : Mon Apr 29 2013 - 19:05:26 CEST