| Summary: | Table of Figures: Wrong on a multi page view | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Andreas Heinisch <andreas.heinisch> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | emanuele.gissi, heiko.tietze, sdc.blanco, telesto, vmiklos |
| Priority: | medium | ||
| Version: | Inherited From OOo | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=130318 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 89606, 130318 | ||
| Attachments: | Document showing the bug | ||
|
Description
Andreas Heinisch
2021-12-27 21:07:21 UTC
Created attachment 177162 [details]
Document showing the bug
Code pointer: https://opengrok.libreoffice.org/xref/core/sw/source/core/docnode/node.cxx?r=9d3b6364&mo=27449&fi=773#813 On a single page view it works. I confirm the bug in: Version: 7.2.4.1 Build ID: 20(Build:1) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: it-IT (it_IT.UTF-8); UI: it-IT Calc: threaded Confirm that problem appears in "multiple-page view" but not in "single-page view" Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: e63fe68fb1d0915b64fdf63f7fa6eed866fa3a0d CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_DK); UI: en-US Calc: CL Also in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 Miklos, do you have an advice here? I'd love to see bug 130318 implemented (ToC everywhere) but Andreas considers this issue as a blocker. No idea off the top of my head, unfortunately I see the single page view ~all the time. So for the single page view it works, but just in the top case. Is there a possibility to check if a figure index is contained or before the next outline node? My approach does not seem to work in the patch (searching my chapter node and going down till I find one with greater index, and then checking if the frame lies within): https://gerrit.libreoffice.org/c/core/+/125727/6/sw/source/core/doc/doctxm.cxx#774 Thank you Dear Andreas Heinisch, 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 |