Description: see 'Steps to Reproduce', 'Actual Results' and 'Expected Results' Steps to Reproduce: 1. Open 'Paragraph Style' dialog from 'Styles' 2. Switch to 'Tabs' tab 3. Move focus to input field beneath 'Position' 4. Start typing e.g. '5.20 cm' Actual Results: Caret position moves to the beginning of input field after each keystroke disrupting further typing, e.g. typing '5.20 cm' results in 'mc 02.5' Expected Results: Caret position should follow 'normal' behaviour, e.g. after each keystroke move behind typed character, typing '5.20 cm' results in '5.20 cm' Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.0.3 Build ID: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62 CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk2; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded
I can confirm this bug occurs in 6.2.0.3 and was not present in 6.1.4.2 on Linux. In Steps 1 & 2, I right-clicked the Default Style > Modify > Tabs. I selected the entire Position text box with ctrl-a and type 1. The cursor postion (represented by the underscore) was "_1". It should have been "1_".
I confirm that the field has a problem for me too. The details are slightly different: When I type in the input field, I can’t change any text. So in summary I can’t set tab stop positions numerically at the moment. The left and right arrow keys work, I can also combine them with Shift to select text or with Control to move to word boundaries. Pos1 and End work as well. But any key that would change the content does not work. The Backspace and Del keys simply take me to the beginning of the field. Typing any actual character, numeric or letter, moves the caret one position forward. The field content (the position of the first defined tab stop or “0.00 cm” is none has been defined) is left unchanged in any case. My environment: LibreOffice 6.2.0.3 on Arch Linux, fully updated, tried XFCE and Cinnamon sessions. German keyboard.
The original problem also occurs in W10-x64.
Similar problem here. The tab stop position input behaves really strange (deterministic but different to everything I've ever encountered). Looks like there's some minimal info (0.00 cm) that cannot be deleted during the input, which causes the strange behaviour. It's also impossible to input any unit but cm (in 6.1 the number got converted to cm, now you cannot even enter it). Say we have 0.00 cm entered. Now different types of input (with the same starting position) give different results: a) select all, write 2 => result is 20.00 cm b) put caret at the end, write 2 => no input happens c) put caret at the beginning, write 2 => result is 20.00 cm d) put caret just before the decimal point, write 2 => result is 2.00 cm e) put caret just before the decimal point, press backspace, write 2 => result is 20.00 cm Now start with 13.00 cm, same type of input as in previous cases a) result is 20.00 cm b) no input happens c) result is 56.00 cm d) result is 56.00 cm e) result is 12.00 cm f) put caret between 1 and 3, press backspace, write 2 => result is 23.00 cm While I'm able to type any number (within the bounds) that I need, it's very cumbersome. Like for the other commentators, the bug got introduced in 6.2.x.
I cannot confirm the problem with Version: 7.1.0.0.alpha0+ CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-08-05_04:03:50 Calc: threaded
Dear garavo, 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