Bug 150843 - Percentage Formatted cells are inconsistent in data entry - Leading zeros create different results
Summary: Percentage Formatted cells are inconsistent in data entry - Leading zeros cre...
Status: CLOSED DUPLICATE of bug 133485
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.7.2 release
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-07 09:36 UTC by Jax
Modified: 2022-09-07 12:03 UTC (History)
0 users

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 Jax 2022-09-07 09:36:26 UTC
Marked as MAJOR error as data entry in a spreadsheet is a fundamental basic expectation and would lead to errors in calculation whilst leaving little visual clue to the fault.

If a cell is formatted to Percentage Format (to 2 decimal places in this example but that's not important), then typing the following figures gives inconsistent results.

10   gives  10.00%
.1   gives  10.00%    If .1 is pasted, gives 10.00%
0.1  gives   0.10%    If 0.1 is pasted, gives 10.00%
1    gives   1.00%
.01  gives   1.00%
0.01 gives   0.01%

During typing, typed entries starting with a digit are rendered as percentages during typing but entries starting with decimal point (not tested for other locales e.g. decimal comma) assume non percentage format but then applies format after entry.

Anyone entering a column of numbers could easily be caught out by this.  It would appear like data entry error.

Reproduceable:  Always

Expected:  Consistency
Comment 1 Timur 2022-09-07 11:16:03 UTC
No repro. Please attach a sample ODS.
Comment 2 Eike Rathke 2022-09-07 12:03:05 UTC
Earlier versions like the 6.4.7.2 release set in the Version field had a bug that starting input with a decimal separator character cleared the trailing % character (as with any other non-digit character), hence input wasn't a percentage. This was fixed long ago. It's anyway recommended to upgrade from such an old legacy version.

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