diff options
| author | Michael Stahl <mstahl@redhat.com> | 2017-08-18 17:25:17 +0200 |
|---|---|---|
| committer | Michael Stahl <mstahl@redhat.com> | 2017-08-18 17:42:33 +0200 |
| commit | 6a018363791945b6fd7f04f2aa311e4f4753f6aa (patch) | |
| tree | 38ca7fb3f4c948ae8193e00c276860e87fc405c7 /dbaccess | |
| parent | e182760b16f9d71d93907c4bba86d26a466d8918 (diff) | |
tdf#99692 sw: fix the fix: don't set bNullContent if node was split
When showing the redlines in rhbz908615-13.odt, the following assertion
happens:
Assertion `IDocumentMarkAccess::IsLegalPaMForCrossRefHeadingBookmark(rPaM) && "<CrossRefBookmark::CrossRefBookmark(..)>" "- creation of cross-reference bookmark with an illegal PaM that does not expand over exactly one whole paragraph."' failed.
This is because in DocumentContentOperationsManager::MoveRange() the
flag bNullContent is set after the node has been split; in this case the
nContent is of course always 0.
Later the function then restores aSavePam to the index 0 of the next
node, when it actually shouldn't do anything because the JoinNext()
already positioned it correctly at the merge-index of the re-joined node.
(regression from 850795942b3e168cab8ce88b4f2b421945ff29ca)
Change-Id: I64d50e70b19e2fd81537a9771fa8706898b17642
Diffstat (limited to 'dbaccess')
0 files changed, 0 insertions, 0 deletions