Description: In a Date control, in design mode, if try to set "Date min" property to a value lower than 1/1/1800 it changes to 1/1/1600 without any warning. Also is is not possible to delete "Date min" value. So, in production, the mínimum date that is possible to introduce in a date control is 1/1/1600. Steps to Reproduce: 1. Create a writer document (or a Base form, or a Basic form, or may be in Calc or Impress) 2. Insert a Date field control 3. In design mode, set "Date min" property value lower than 1/1/1600 4. Lost focus on "Date min" property, the value is changed to 1/1/1600 without any warning 5. Close design mode 6. Introduce a date lower than 1/1/1600 and push Enter, the date is changed to 1/1/1600 Actual Results: * Not possible to set a lower than 1/1/1600 "Date min" property value * Not possible to introduce a value lower than 1/1/1600 in a date field control Expected Results: * Set any "Date min" property value, also no value (no limit) or at least from "1/1/0001" to "31/12/9999" which is the range in most of databases * Introduce any date in the control 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: es-ES Calc: CL
*** Bug 150588 has been marked as a duplicate of this bug. ***
Bug 150588 is almost the same just with max instead of min. ("if try to set "Date max" property to a value greater than 1/1/9999 it changes to 1/1/9999 without any warning. Also is is not possible to delete "Date max" value. So, in production, the maximum date that is possible to introduce in a date control is 1/1/9999. ")
(In reply to Eike Rathke from comment #2) > Bug 150588 is almost the same just with max instead of min. Yes, that is true, but I've been said "if something different, different bug"
Created attachment 182012 [details] Test writer document with a data field control
Confirmed: LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
I have sent a patch set https://gerrit.libreoffice.org/c/core/+/138845 to discuss. Changes in the patch, solve the problem of view data in a date field control in most databases, which usually their date range goes from 1/1/0001 to 31/12/9999, but still maintains limits on the range of dates that can be viewed. A solution that removes all limits would be better, but I am not able to implement it without help. In any case, the patch extends the range of supported dates to dates before 1/1/1600, which in my opinion is too limiting date, and on the other side it extends the range so that it allows to enter the "magic" date 9/9/9999 which is widely used by database users as the "end of the world" date (the forever date in ranges from-to). This patch could solve too tdf#150587 extending the limits of "Date min" and "Date max" to more reasonable limits
Confirmed with "Date min" and "Date max". LibreOffice 7.4.0.3 OS: Linux 5.19 (release supplied by Arch Linux); UI render: default; VCL: gtk3 Locale: es-VE (es_VE.UTF-8); UI: es-ES
Also 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
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