summaryrefslogtreecommitdiff
path: root/editeng/source
diff options
context:
space:
mode:
authorMiklos Vajna <vmiklos@collabora.com>2025-04-04 09:43:43 +0200
committerMiklos Vajna <vmiklos@collabora.com>2025-04-04 14:31:11 +0200
commite435dc6ca1a898f4e806127257c9acc627c080cc (patch)
tree06b2c1f1eb13132c6be63b8b02c3549cfef04c57 /editeng/source
parent1886ecf7ee10cc51ca90fe1365e4a8ef2a1b6f27 (diff)
tdf#165941 DOCX import: fix unhandled exc while removing dummy para in table
The bugdoc can't be opened in Writer but Word considers it valid. This went wrong in commit 97f9af714ea1c46e498fa99f7ca34fc1708d38a6 (Related: tdf#125038 DOCX import: fix unexpected linebreak inside IF condition, 2019-10-30), because now we may have a range that is crossing a table of section boundary: this is a valid range for a field start/end in Word, but not in Writer. Fix the problem by handling exceptions from createTextCursorByRange() in DomainMapper_Impl::RemoveDummyParaForTableInSection(): we already assumed previously that the created cursor may be an empty reference, just the exception case was unexpected. The bigger problem is that Writer fields can't expand to multi-paragraph content while Word can do that, but that was a problem before the above commit, so is not addressed here. Change-Id: I718b702e68da5bf90eb4af95bb179d2e33abadc3 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/183710 Tested-by: Jenkins Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
Diffstat (limited to 'editeng/source')
0 files changed, 0 insertions, 0 deletions