Description: When a cell contains misspelled text, right-clicking the cell will immediately enter edit mode and present the autocorrect context menu (see attached GIF). This goes as far as entering edit mode for the right-adjacent cell when misspelled text overlaps with that neighbouring cell (see attached GIF). Interestingly, this does not happen in v5.4.73.2, where only the cell containing the misspelled word itself is affected. Furthermore, cells to the left aren't affected by an overlapping misspelled word from the cell to its right (see attached GIF). Steps to Reproduce: 1. Type a word with a spelling error into a cell (and make the word wider than the cell itself). 2. Right-click the misspelled word (either in the original cell or the cell to the right). Actual Results: Calc enters edit mode for the cell containing the misspelled word, marks the whole word, and shows the autocorrect menu. Upon left-clicking anywhere else, the cursor remains with the misspelled word. Expected Results: The regular right-click context menu for a cell, not it's containing text, should be shown. For text overlapping a cell to the right, the right-click context menu for the cell to the right should be shown (when clicked on it where the misspelled text from the cell to its left is overlapping). Reproducible: Always User Profile Reset: No Additional Info: Version: 25.2.1.2 (X86_64) / LibreOffice Community Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49 CPU threads: 16; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL threaded
Created attachment 199981 [details] Right-clicking a misspelled word will enter edit mode for the affected cell and show the autocorrect menu
Created attachment 199982 [details] Cells to the right are affected by overlapping text, but not cells to the left
*** This bug has been marked as a duplicate of bug 80751 ***
OMG, duplicate of a bug reported in ... 2014! Worse yet, Kohei Yoshida called it "intended behavior", ignoring user experience and how other software behaves.
I changed this bug to "New" because (1) bug 80751, which this one is supposed to be a duplicate of, is marked as "RESOLVED NOTABUG" even though this behaviour is unexpected and a bug, and because (2) the current bug report is about overlapping content in addition. If the behaviour to enter edit mode and override a user's expectation to see the regular right-click context menu is intended, it should either not do so with overlapping text for the right-adjacent cell, or it should do so consistently and also affect the left-adjacent cell in the same way. Marking bugs as DUPLICATE and NOTABUG without any arguments, discussion, or feedback is ... frustrating at best. I propose a simple solution: Do like Firefox does! Add the autocorrect actions on top of the regular context menu actions. No more inconsistent behaviour, no need to be smug about "we want it to work this way and don't care about your experience", relatively easy to implement, and enhances autocorrect for all LO components.
You can't set up your own report as new. In any case, this is not a bug, but a possible request for improvement. Why do people always think that their expectations are the expectations of all users?
Thank you for resetting the status to UNCONFIRMED. I see the distinction between NEW and UNCONFIRMED now, and I was inconsiderate when I changed the status to NEW. I still think the current behaviour is more of a bug than a request for improvement. It is not just the inconsistency between right and left overlapping cells, but also the fact that Calc enters edit mode after a right click on multiple marked cells when the cell under the mouse pointer happens to contain a misspelled word. All this looks like autocorrect was implemented without considering that it would break the UI experience that Calc itself established (not the user). Autocorrect blocks users from interacting with their spreadsheet.
Rant: Reporting a bug is work. No, not nearly as much work as coding, but enough to keep most users from even thinking about reporting anything. When you see one bug report, you might be looking at a single basement dweller venting frustration. But you might also be looking at the one user saying what thousands of others think. What frustrates me the most about these kind of discussions and dismissing users as "main characters", "it's working as intended by the godly programmers", "it's free, stop complaining", ..., is that I love the idea of OSS, but that I can't do more than donating a few bucks and "spreading the word". My experience at university was that whenever MS Word crashed people said "Oh well, looks like I'll have to start over again. Thankfully I only lost 3 hours of work". When LO behaved quirky, people exploded "WTF?! I can't work with this! Back to MS Office! And you better send me a DOCX next time, instead of one of those ODT!!!" It is unfair that OSS like LO is being held to a higher standard than the big player MS, and that OSS doesn't have nearly as much funding as deserved. Please don't make things worse by working against OSS enthusiasts and dismissing reports as "invalid because of some technicality". When I try to convince people to use LO instead of MS, I really don't need LO to stab me in the back when MS already cut off my legs. We both want LO to succeed!
Version 25.2.1.2 Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49 CPU threads: 8; OS: Windows 11 x86_64 UI render: Skia/Raster; VCL: win Locale: en-US; UI: en-US Calc: threaded Marking as new. I do believe this is a bug. The behavior when right-clicking the misspelled word in both of adjacent cells should be consistent.