Description: Wrong spelled underlining gone after pressing enter caused by autocorrection capitalize Steps to Reproduce: 1. Open the attached file 2. Press enter after lightning (last word) 3. lightning gets capitalized red line gone Actual Results: Not wrong spelled anymore Expected Results: Line should show Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.2 Build ID: c01aa64b6c3d89ebe5fe69c28c7adb24eb85249c CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded
Created attachment 164401 [details] Example file
Not sure if this is because of autocorrection.. but surely not present in Version: 6.1.6.3 Build-ID: 5896ab1714085361c45cf540f76f60673dd96a72 CPU-Threads: 4; BS: Windows 6.3; UI-Render: GL; Gebietsschema: nl-NL (nl_NL); Calc: CL @Raal Adding you for if you want to bibisect something (I will do it at some point if not done before), as this is 'slightly more pressing' in the whole flood of reported bugs; else this goes lost the the big pile.. as QA can't keep up with the quantity of bug reports (or should I say example reports/ or symptom reports/ the software contains the 'bug'.. I only report the (side)effects/results) demonstrating a (potential) flaw.
Created attachment 164411 [details] printscreen from LO 7.1 win works for me in Version: 7.1.0.0.alpha0+ (x64) Build ID: 1db7decf3fb172542f5fce03ce7bf0cb310d1ffc CPU threads: 4; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win
Created attachment 164439 [details] Example file reduced This is the file with the image anchored to it.. and with everything at stock settings (incl autocorrect and such) lightning is changed to Lightning pressing enter... happens on my mac too.
I didn't have German, so I changed the language to Finnish. No problem observed as described here. Arch Linux 64-bit Version: 7.1.3.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 8; OS: Linux 5.12; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: fi-FI 7.1.3-1 Calc: threaded
Dear Telesto, Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Not reproducible for me with Version: 7.3.4.0.0+ / LibreOffice Community Build ID: 614049f7bc962f48676a19b5e6e2ded2862280d6 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Ubuntu_20.04_x86-64 Calc: threaded Best regards. JBF
Dear Telesto, 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 Telesto, 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