Bug 65267 - FORMATTING: Inputting times as HHMM to cells formatted as HHMM produces unexpected results
Summary: FORMATTING: Inputting times as HHMM to cells formatted as HHMM produces unexp...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Spreadsheet (show other bugs)
Version: 3.6.6.2 release
Hardware: All All
: high minor
Assignee: Not Assigned
QA Contact: Jorendc
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-02 14:20 UTC by tulitomaatti
Modified: 2013-10-07 23:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description tulitomaatti 2013-06-02 14:20:17 UTC
Problem description: 

When trying to input a time, for example a quarter past four in the afternoon as HHMM, that is 1615, to a cell with a format code HHMM, the result is something else than 1615. Inputting 1615 results to 06/02/1904 00:00:00. It seems to me that the input is being interpreted as a date.

Steps to reproduce:
1. Set cell format code to HHMM
- Right click on cell, choose Format cell...
- Set format code to HHMM and click ok. 

2. Input time as HHMM
- Enter a time, for example 1615 and press enter.

3. Cell displays now 0000 and holds a wildly different time.


Current behavior:

Cell displays 0000 and contains a date from 12/30/1899 00:00:00 to 06/16/1906 00:00:00 depending on the time entered, assuming that a time from 0000 to 2359 is entered. 

Expected behavior:

Cell displays the time entered and contains the time entered. 
              
Operating System: Mac OS X
Version: 4.0.2.2 release
Comment 1 Jorendc 2013-06-02 14:23:08 UTC
Thanks for reporting.

I can reproduce this using Linux Mint 15 x64 with LibreOffice 4.0.3.3, as well with LibreOffice 3.6.6.2. -> NEW

Priority:
* Minor: does makes it substantially harder to create high quality work
* High: a bit more then default priority

Kind regards,
Joren


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.