Bug 131439 - Editing date - weird prompt behavior
Summary: Editing date - weird prompt behavior
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice Online
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-20 12:22 UTC by Adam Mizerski
Modified: 2021-02-09 12:56 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
screencast (830.11 KB, video/webm)
2020-03-21 16:01 UTC, Adam Mizerski
Details
<spam> (2.49 KB, text/plain)
2020-08-01 07:38 UTC, Reyy kakeru
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Mizerski 2020-03-20 12:22:01 UTC
Version: 4.2.0 (git 48938d4)

Steps to reproduce:
1) create new spreadsheet
2) select a cell, change format to date, enter something (like 01.01.2020)
3) click on the input line  and try to edit the date

Expected behavior: it should work correctly, like editing text and numbers.

Actual behavior: Focus goes from input line to cell itself. When typing, letters and digits appear on the right side of prompt and punctuation marks appear on the left side.
Comment 1 Oliver Brinzing 2020-03-21 09:30:50 UTC
Thank you for reporting the bug. 

Which LO version did you use?
Please copy information from Menu "Help/About LibreOffice"

Can you please add a screenshot?

I have set the bug's status to 'NEEDINFO'. 
Please change it back to 'UNCONFIRMED' once the requested info is provided.
Comment 2 Adam Mizerski 2020-03-21 16:01:41 UTC
Created attachment 158853 [details]
screencast

In this screencast:
- I change the format to Date
- type "01.01.2020"
- show the prompt moving to cell from input line
- delete "01.2020" from the end
- type "01.2020"
Comment 3 neolift 2020-04-18 05:44:41 UTC Comment hidden (spam)
Comment 4 Reyy kakeru 2020-08-01 07:38:00 UTC Comment hidden (spam)
Comment 5 Adam Mizerski 2020-08-04 09:15:05 UTC
Now I have version 4.2.5 and it looks like it was resolved.
Comment 6 Xisco Faulí 2021-02-09 12:56:03 UTC
Thanks for retesting the issue with the latest version.
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been
identified.