Bug 150571 - Dates changed on a form without warning the user (date max).
Summary: Dates changed on a form without warning the user (date max).
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
3.3.0 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Fields
  Show dependency treegraph
 
Reported: 2022-08-23 21:35 UTC by jcsanz
Modified: 2024-08-31 03:16 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Test database (11.85 KB, application/vnd.sun.xml.base)
2022-08-23 21:43 UTC, jcsanz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jcsanz 2022-08-23 21:35:19 UTC
Description:
Dates that are entered in a form, in a "date field" control with a "date max" property assigned, if they are greater than that date, they are modified without warning the user.

Steps to Reproduce:
1. Create a table with at least one DATE field
2. Create a form to edit such table, with a "Date field" control to modify the DATE field.
3. Modify the date field control to assign a "Date max" property (or leave the default 31/12/22000)
4. Save the form
5. Open the form to fill data
6. Introduce in the date control a date grater than "Date max" assigned in step 3
7. With the cursor in the date field, click on "Save record" button on the Form navigation tool bar
8. Close the form and test data in the table

Actual Results:
On step 7, if you have an autovalue field, it is assigned a new value to it, making it appear that the record has been saved correctly.
The date introduced seems as it has been saved (without any modification).
The real date saved in the table is the "Date max" date

Expected Results:
On step 7, a warning message about the invalid date.
No data saved until date is in range.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.4.0.3 (x64) / LibreOffice Community
Build ID: f85e47c08ddd19c015c0114a68350214f7066f5a
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL
Comment 1 jcsanz 2022-08-23 21:43:21 UTC
Created attachment 181990 [details]
Test database

Database with a table and a form to test.
Record with id,s 8 and 9 has been obtained introducing the "8/8/8888" date
Comment 2 jcsanz 2022-08-24 20:34:12 UTC
Component changed to UI because it seems a control problem, not a Base problem
Comment 3 gmolleda 2022-08-26 17:51:47 UTC
Same behaviour in LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4

In step 3 the "Date max" is 31/12/2200 and not 31/12/22000.

Esperanto estas la plibona universala lingvo, la angla diskriminacias.

Sama konduto en LibreOffice 3.3.0
OOO330m19 (Konstruo:6)
etikedo libreoffice-3.3.0.4

En la paŝo 3 la "Dato max" devas esti 31/12/2200 kaj ne 31/12/22000.
Comment 4 Stéphane Guillou (stragu) 2022-08-31 10:17:41 UTC
Confirmed with:

Version: 7.4.0.3 / LibreOffice Community
Build ID: f85e47c08ddd19c015c0114a68350214f7066f5a
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded
Comment 5 QA Administrators 2024-08-31 03:16:17 UTC
Dear jcsanz,

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