Description: If cursor placed inside big paragraph (a few pages) cursors PageStyleName property shows wrong page style name (shows style of the page where paragraph starts). So I haven't found a way to get current valid page style name. Steps to Reproduce: 1. Create big paragraph 2. Set first page style to First Page 3. go to second page. Check cursor's property Actual Results: page style name of page where paragraph starts Expected Results: current page style name Reproducible: Always User Profile Reset: No Additional Info: Macor to reproduce Sub wrongPageStyleName Dim oViewCursor As Object oViewCursor = ThisComponent.CurrentController.getViewCursor() oViewCursor.goToStart(false) MsgBox "First page style is rigth "+oViewCursor.pageStyleName oViewCursor.jumpToNextPage() MsgBox "Second page style is wrong (at start)) "+oViewCursor.pageStyleName oViewCursor.jumpToEndOfPage() MsgBox "Second page style is wrong (at end)) "+oViewCursor.pageStyleName End Sub
Created attachment 149013 [details] Test document with big paragraph. First page style set to "First page", others to default.
I can reproduce it in Version: 6.3.0.0.alpha0+ Build ID: f8ca6e0a59bff51fcb09af4fa6d9cd458b32f223 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded and LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 however, I don't know whether it's an issue or not... @Miklos, do you know why on second page it returns the page style from page 1 ?
Yes, this is indeed a bug, at least in the ViewCursor case. I think the reason for the current behavior is that we fetch the paragraph properties for the cursor and expose PageStyleName based on a that, which means that in case the paragraph spans over multiple pages, we expose the page style of the first page. So the behavior is not too surprising, but the ViewCursor (which is aware of pages) could be indeed fixed to take multi-page paragraphs into account.
Dear Georgy, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Looks ok in Version: 7.2.0.0.alpha1+ / LibreOffice Community Build ID: 42d2b2d55a27f11153ea1713737d93540a19211d CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded