Open attachment 189413 [details], and use this code: sub TestContentControlImportedObjects paragraphs = thisComponent.getText().createEnumeration() para1 = paragraphs.nextElement() runs1 = para1.createEnumeration() run1 = runs1.nextElement() para2 = paragraphs.nextElement() runs2 = para2.createEnumeration() run2 = runs2.nextElement() MsgBox run1.getString() MsgBox run2.getString() MsgBox run2.ContentControl.getString() end sub The document has two paragraphs, each having a content control with a placeholder text. Because the first one is a block control (which content includes the respective paragraph), and the second is an inline control (contained in the paragraph, and the content includes only a run), these two are imported differently (as of 2023-09-07): the first one as a field, and the second one as a content control. The three MsgBox calls in the end of the code are expected to show the same "Click or tap here to enter text." string. However, the second call showing "run2.getString()" produces an empty message. This happens because lcl_CreateContentControlPortion in sw/source/core/unocore/unoportenum.cxx is called with pUnoCursor pointing to the end of the paragraph. Looks like it needs to take into account the values of rAttr (and respective SwContentControl), and pPortions, which may contain the range that should become the actual cursor.
Repro Arch Linux 64-bit, X11 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5e9c8d21874eea8cb5adf2ecab1905295af2308f CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 26 September 2023
Dear Mike Kaganski, 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