Project

General

Profile

Bug #9876

FILL-IN: date format with long year format component: incorrect INPUT-VALUE

Added by Vladimir Tsichevski over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
15823
version_resolved:
reviewer:
Hynek Cihlar
production:
No
env_name:
topics:

9876.p Magnifier (516 Bytes) Vladimir Tsichevski, 04/05/2025 05:59 PM

Related issues

Related to User Interface - Bug #7515: FILL-IN: editing dates issues WIP

History

#1 Updated by Vladimir Tsichevski over 1 year ago

  • version_reported set to 15823
  • File 9876.pMagnifier added
  • reviewer Hynek Cihlar added
  1. run the 9876.p procedure. It will show you a date type FILL-IN
  2. enter the value 01-02- 1 (with 5 spaces before the last 1) into a field
  3. Press Enter to trigger the event, which prints the SCREEN-VALUE (matching the visible FILL-IN value in both OE and FWD) and INPUT-VALUE, which resolves to 01/02/2025 in OE (using the current year, 2025) but 01/02/2000 in FWD.

Note: typing spaces directly is impossible, you must first type digits, then use a delete region operation to remove these digits, effectively converting the deleted region to spaces.

#2 Updated by Vladimir Tsichevski over 1 year ago

The described behavior applies once issue #9846 is resolved. With trunk rev. 15823 (current), the INPUT-VALUE is undefined, which is also incorrect.

Also, the on-screen value changes to 01-02-2001, which is also incorrect: both the value and format differ from the expected.
Also, this on-screen value change must not happen at all.

#3 Updated by Vladimir Tsichevski over 1 year ago

  • Related to Bug #7515: FILL-IN: editing dates issues added

Also available in: Atom PDF