Created attachment 125237 [details] attached a document with footnotes (it can be used to reproduce the problem) So, if a document is not refreshed(via the usual way with XRefreshable, I'm specifically talking about the Writer application, because that's where this situation was found), two things happen: a) The page numbers reported by XPageCursor are off(confirmed on both 5.1.2.2 and 4.2.8.2) b) The footnotes are not loaded at all (confirmed on 4.2.8.2). In effect, on a XSearchable search they do not show up in the results, but if the document is refreshed prior to doing the search, they show up just fine. My suggestion is that either this should be specifically mentioned in the documentation and reflected in the UNO API examples or it should not be required for a user to refresh the document, and it should happen implicitly as part of the UNO API default behaviour. I view this as the intuitive way of solving this problem. I look forward to your thoughts on this. Thank you for taking the time to read the bug report
My concern is mostly on the consistency and expecations side. Because if this was mentioned in the documentation, I'd be like, I'm ok with that because I read it was a problem and I should take care of it, but I didn't find it in the docs. On the other hand, I feel like this is a sane default to have, maybe ? not sure. I mean, refreshing the document by default would incur some additional processing. Maybe the workload generated by that would be too high?
Would you mind providing a minimal, but complete code example that could be used to reproduce the issue together with the document?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170131
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170301