View Single Post
Old 12-08-2020, 12:22 PM   #9
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,884
Karma: 6120478
Join Date: Nov 2009
Device: many
All of that said, there really is no sound reason to not properly handle nesting (or at least try to).
My worry when doing this is that other attributes will be copied as well including id attributes which would and could mess up Anchor Updating after splitting is done.

I have copied the approach of Split at Cursor and tried implementing it with Split At Markers.
I will tentatively commit this change to master and we can test it to make sure that any id attributes on any nested tags at break points do not cause problems.

If they do end up causing issues, we will revert it and Split at Cursor will be the only way for you to handle this case on a one by one basis.

Thank you for your bug report.
KevinH is offline   Reply With Quote