Description: The attached document asserts in dbgutil for me with: sw/source/core/txtnode/swfont.cxx:1064: Size SwSubFont::GetTextSize_(SwDrawTextInfo &): Assertion `!"this is presumably dead code"' Steps to Reproduce: 1. Load Document Actual Results: dbgutil build asserts, release build shows fieldname and tags as content Expected Results: Ideally, field result of "February 14, 2014" as seen in msword screenshot Reproducible: Always User Profile Reset: No Additional Info: screenshot of word, LibreOffice 7.2 and 7.3 attached. bisect of the LibreOffice 7.2 to 7.3 changes gives: commit a4432eb0946c0bc775b3d30b634bef5d66544f8d Date: Wed Nov 24 14:50:12 2021 +0300 tdf#104823: support for sdt plain text fields This is a squashed commit containing set of changes:
Created attachment 183585 [details] comparisons of word and LibreOffice 7.2 and 7.3
Created attachment 183586 [details] source document
Yes, I can reproduce the problem. The document has an <w:sdt> but then inside that, there is a FORMTEXT field. Additionally, the assert is added in commit 19a559b0ec9b806519c405651d6d2b2e14712b4a (sw: SwSubFont::GetTextSize_() assert on presumably dead code, 2019-10-14), perhaps Michael S and Vasily should agree if that assert is valid or not.
Problem was also reproduced. Not sure about assert by itself: it looks unrelated, because we have problems much earlier during insertion of field into sdt field: this wasn't expected. No suggestions on fixing yet.
Dear Caolán McNamara, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug