When double clicking on a cell to edit a time value, the input format should match the format assigned by the user to the cell. For example, a cell has been assigned a standard format of "13:37", which is the 24 hour military format, "HH:MM". However the cell is displayed for editing in the full 12 hour format "HH:MM:SS xM" where x may be either A or P. If the column width is set to fit the "HH:MM", the edit forces a second line containing the seconds and the AM/PM. An the original value of "14:00" is displayed for editing as: 02:00: <on line 1 00 AM <on line 2 and the user is forced to not only change the time value from "00" to "30" but also drop down a line and change AM to PM to get the desired result of "14:30".
Hi Aprax, I don't reproduce with LO 4.4.4.3 Build ID: 2c39ebcf046445232b798108aa8a7e7d89552ea8 & windows 7 Home Premium Can you provide a spreadsheet showing this behaviour?
Created attachment 117213 [details] Sample of issue It is pretty easy to create the attached sample that demonstrates the issue. The attachment contains a cell with Notes that may help understand the issue.
Thanks for the sheet. Issue appears only with US locale for me. I don't see it with french or UK locale, where default format for Time is HH:MM:SS.
The issue does, in one sense, involve the 'default', because it uses the default format for the editing despite the fact that I have set the format to be "13:37" and expect the editing to use the "13:37" format and NOT convert "14" to :02" and magically pull a "PM" from the air. Yes, there would be no issue if I was willing to use the default format for all my time columns except some sheets would be 3 feet (1 Meter) wide on a much smaller monitor or the font would have to be very small.... To say it again, I would like the editing to use the user's selected format, i.e. that was consciously and with specific purpose chosen by the user, for a cell. LO does the right thing for Date and Number formats and should for Time formats.
(In reply to Aprax from comment #4) > I would like the editing to use the user's selected format, > i.e. that was consciously and with specific purpose chosen by the user, for > a cell. > > LO does the right thing for Date and Number formats and should for Time > formats. I agree -> NEW. Repro with US locale. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ (x64) Build ID: e92a8b92072284fd7c37d7bb3e1e8fe72a185f35 TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-07-22_21:46:26 Locale: fi-FI (fi_FI)
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
You sent an email asking: ======================= "If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 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)" If the bug was present with 3.3 - set version to "inherited from OOo"; If the bug was not present in 3.3 - add "regression" to keyword ======================= I took a backup image of my system I uninstalled v 4.4.4.3 and then installed v 5.2.1.2 the problem still exists I uninstalled v 5.2.1.2 and then installed v 3.3.0.4 the problem still exists so I'll set version to "inherited from OOo I didn't test with v 5.1.5.x, that would be redundant after v 5.2.1.2 I restored my backup image to 4.4.4.3 because there are still rendering issues with any of the v 5 releases although 5.2.1.2 wasn't quite as bad as earlier v 5's. There was NO rendering issue with v 3.3.0.4 at all, but rendering is a different bug, I just wanted to explain why I've stayed with v 4. J
** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
The problem still exists in 5.3.6.1, see screenshots which show formatting and editing.
Created attachment 136627 [details] just formats shows default Time format and user selected format
Created attachment 136628 [details] editing format shows that editing format does not reflect the user chosen format for the cell
Looks like this won't be fixed, too bad
** 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! Warm Regards, QA Team MassPing-UntouchedBug
The problem still exists in V 6.2.0.3 (x64). The Resolved as Fixed is a lie.
Created attachment 149787 [details] example of editing format
Dear Aprax, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Version: 7.0.1.2 (x64) Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-CA (en_CA); UI: en-US Calc: threaded
Works for me now, thanks.