https://bugs.documentfoundation.org/show_bug.cgi?id=145248

            Bug ID: 145248
           Summary: EDITING CELL contents in the contents/formula bar
                    produces unexpected result
           Product: LibreOffice
           Version: 7.2.1.2 release
          Hardware: All
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]

Description:
Cell contents may be edited either with a total change by simply selecting the
cell and typing new contents into the contents/formula bar or,  selective
modification directly in the cell or the contents/formula bar - by
double-clicking the cell and typing appropriately in either of the two
locations.
When the amendments are typed into the CELL then all the selection, erasure and
overtyping procedures perform as anticipated.
However, when the amendments are effected in the contents/formula bar then
there are anomalies in the selection process. I have observed content
corruption but as yet, have been unable to identify and therefore demonstrate
the immediate actions which precipitated that corruption.
What is demonstrated herewith is the persistent anomaly when a singleton
character is the starting point for selection and amendment.
Attached are both the simple .ods and a .mp4 demonstrating the anomaly.

Steps to Reproduce:
The attached .mp4 demonstrates the actions on the attached .ods.
You will notice that the effect is predominant when the singleton "a" character
at the penultimate word location in the text is determined as the starting
point for a left wise selection.
The effect may sometiomes be "masked" by other intermediate (and indeterminate)
activities around the sheet but will return.
Sometimes, an alternate valid selection preceding the rogue will negate the
effect of the rogue singleton starting point but clicking outside the cell and
double clicking the cell and commencing with the selection attempt in the
contents/formula bar will always reproduce the issue.

Precise Steps;
Double click on B8 to commence editing
Cursor anywhere in the cell and simply click and move to select some text.
Abandon it and select another chunk
Moving left or right still selects a chunk
Click outside the cell to deselect
NOW
Double click B8 again
Go to the cell contents line and proceed to edit there
Place your cursor in the middle and start to select a chunk to the left
Release the cursor and observe that the text is selected in both the cell and
the content.
Now move the cursor to the right of the singleton character “a” - the
penultimate “word” and move the cursor ONE character left.
Observe how just the singleton is selected and a “No Entry” symbol is produced.
If the cursor is moved further to the left it will at its own volition either 
“select” a larger chunk or simply continue to display the "No Entry" symbol - I
have even experienced "corruption" of the contents when the mouse is released.
Without deselecting the character move the cursor out of the box and then
re-enter the box at the extreme left - everything is selected
Again, without deselecting, exit and re-enter the box at the extreme right.
My experiments indicate that if Ctrl+C is executed whilst the text is selected,
it is copied to the clipboard. However, if another mouse click is effected
without the copy action then the selection is “lost”.
It would be nice to assume it’s some kind of “select to here” functionality but
the activation is random so the function is not much use.

Actual Results:
See .mp4 attached

Expected Results:
The same result for both the cell and the content/formula bar


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 7.2.1.2 (x64) / LibreOffice Community
Build ID: 87b77fad49947c1441b67c559c339af8f3517e22
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: sv-SE (en_GB); UI: en-GB
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to