Description: After adjusting my tabs and saving the document, they appear out of order when reopening. They were therefore not properly saved. Steps to Reproduce: 1. Create 2 tabs: the 1st justified on the left, the 2nd on the right with dotted lines 2. Save and quit. 3.Reopen the document to see the bug. Actual Results: Many right-justified tabs with dotted lines have disappeared. Expected Results: The reopened document should be identical to the one that was saved. Reproducible: Always User Profile Reset: No Additional Info: I can produce screenshots or documents illustrating the bug if you give me the possibility.
Created attachment 180958 [details] An example of thix bud is on page 2. Page 2, Roman numeral tabs are never restored after reopening a correctly configured and saved document.
The tab stop is fixed outside the page border. If the edit window is wide enough to include the (not shown) tab stop, there is no issue. Side bar occupied space counts here. Tested with: Version: 7.2.7.2 (x86) / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-MX (es_MX); UI: en-US Calc: threaded Tested with: Version: 7.3.2.2 (x86) / LibreOffice Community Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-MX (es_MX); UI: en-US Calc: threaded Tested with: Version: 7.4.0.0.alpha1 (x86) / LibreOffice Community Build ID: b871abad383583f02eb49c7e49aeae01f6941072 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-MX (es_MX); UI: es-ES Calc: threaded For me, the question is: A tab stop must be taken into account if falls outside the page border?
Created attachment 180975 [details] Tabs not correctly saved Page 1: the document correctly saved Page 2: the same document when reopened
- Luc, you have assigned yourself to this bug. You will solve it? - You can not confirm yourself the bug, you need to wait others to check it.
Lucy, could you please also test, if behavior is still present in latest version 7.5.3? => NEEDINFO
Dear Luc Dupuis, 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
Dear Luc Dupuis, 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-FollowUp