While switching with TAB key between different fields of Bullets and Numbering > Position dialogue and entering new values for indents and so on the entered value is not recognised until you switch to another field of that box. This would be a minor flaw but when you enter the last value and hit the TAB key the cursor goes to “Default” button and hitting the ENTER key to confirm the new values and close the dialogue sets back the indent values to the default. The solution would be to hit TAB+SHIFT keys instead TAB key only (which is less convenient and obvious). However it would be desired to redesign the dialogue to prevent the cursor to jump to the “Default” button right after the last indent value was set.
Confirmed. Win 7 Pro 64-bit, Version: 4.4.2.2 Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6 Locale: fi_FI
Migrating Whiteboard tags to Keywords: (needsDevEval) [NinjaEdit]
This only seems to be the case on Windows. Linux puts the focus on something unseen and when you hit Enter, it hits OK.
The tab itself is part of the tab sequence and after Cancel you can use left/right to go to Image/Customize. But the issue is about tab after "Indent at" that goes to Default. What I cannot understand is why input shouldn't be accepted unless you change the focus. At least for me it works (eg. Aligned at: .5 -> Enter and the dialog closes).
Dear Marek, 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 Marek, 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