When selecting a block of text to spellcheck, the direction of selection makes the difference between correct spelling error detection and false positives.
Steps to Reproduce:
Create a new document. Enter the following two lines of text.
Do not literally type the text in brackets. Instead, press those keys.
This is a test.[press Enter]
This is az test.[press shift up arrow]
All text should now be highlighted. Click spellcheck tool button. Spellcheck finds no errors.
Deselect all text. Select all text with the mouse by clicking at the end of the text (lower right) and dragging to the left and up. Select the Tools menu and click "Spelling and Grammar" (optionally, press F7). Spell check finds no errors.
Deselect all text. Select all text from upper left to lower right using either keyboard or mouse. Use any method to do a spellcheck. Now the spelling error is detected.
Dialog box pops up that says "Spellcheck is complete."
Expected to be shown "az" as a misspelled word.
User Profile Reset: No, I have repeated this bug on other people's machines with older versions of LibreOffice.
[Information automatically included from LibreOffice]
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes
Builds ID: LibreOffice 126.96.36.199
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
I did get the same mistake. Spellcheck does not find az as mispelled word.
Version 5.3.2 windows 10 64bit
Arch Linux 64-bit, KDE Plasma 5
Build ID: d69e6321fbb2c9f5b4d30890074a230ee6b39d2d
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4;
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on April 17th 2016
Arch Linux 64-bit
Version 188.8.131.52 (Build ID: e183d5b)
** Please read this message in its entirety before responding **
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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Bug is still present in 184.108.40.206 (x64).
Version: 220.127.116.11 (x64)
Build ID: 4014ce260a04f1026ba855d3b8d91541c224eab8
CPU threads: 8; OS: Windows 6.19; UI render: default;
Locale: en-US (en_US); Calc: group
Bug is still present in...
Version: 18.104.22.168 (x64)
Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805
CPU threads: 8; OS: Windows 10.0; UI render: GL;
Locale: en-US (en_US); Calc: CL
Is this still a thing? Appears to be working for me
Version: 22.214.171.124.alpha0+ (x64)
Build ID: e8b8e7be0b2ad693224cd94062a55610eb69df7e
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
It's true - I can no longer reproduce it!
Arch Linux 64-bit
Build ID: 6b2eff7d69c6e14d89dd33eaa58c01d82c541266
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Built on 4 September 2020
Ah! It's working for me too.
Version: 126.96.36.199 (x64)
Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e
CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US