Bug 158111 - Problem in editing a line in cell with special character '°'
Summary: Problem in editing a line in cell with special character '°'
Status: RESOLVED DUPLICATE of bug 158112
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.6.2.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-08 08:17 UTC by perko.jernej
Modified: 2023-11-13 17:57 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description perko.jernej 2023-11-08 08:17:29 UTC
Description:
When line of cell contains special character '°'(AltGr + 5), problem while writing to cell occurs.
(problem in writing in cell)


Steps to Reproduce:
1. Open new document in LibreOffice calc and select any cell
2. Write any word
3. Add special character '°' (AltGr + 5)
4. Press any key
5. Press Enter to confirm cell
6. Cell text is replaced to something from functions window

Actual Results:
Cell text is replaced to something from functiosn windows.

Expected Results:
What I wrote to cell is kept in cell and displayed.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (sl_SI); UI: sl-SI
Calc: CL threaded
Comment 1 raal 2023-11-08 19:51:24 UTC
No repro with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 41d9584179ef7b4e18eda47c2c0a955df8c087a5
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

but on windows I can reproduce, when AltGr+5 open right panel Functions. You can see keyboard shortcuts Alt+Ctrl+5 in Tools>Customize>Keyboard
Comment 2 Buovjaga 2023-11-13 17:57:30 UTC

*** This bug has been marked as a duplicate of bug 158112 ***