https://bugs.documentfoundation.org/show_bug.cgi?id=147817
Eike Rathke <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #7 from Eike Rathke <[email protected]> --- (In reply to Loren Amelang from comment #6) > The problem in this report turned out to be that it affects not only > currently typed dates in date columns, but the handling of any number in any > column that could possibly be an "M.D" date! It's treated like every other date input because it was specified as date acceptance pattern. This M.D pattern makes no sense in your locale but was forced when added. Hence I say it shouldn't be accepted in such constellation. > Like dollar values... In > columns that are not date formatted! Like any other date input. A display format is not an input mask. > If a column is explicitly set to dates A column is not set to dates. Cells of a column may have number formats applied, that display the underlying numeric value as date. Just enter 2022-10-22 in a cell, then remove all formatting with Ctrl+M and see the value 44856. > you should be able to enter more dates formatted like what you see above your > cell. You format values to not look like dates but numbers and at the same time want the input of a number be accepted as date.. again, number display formats are not input masks. > And even more importantly, in columns that are NOT formatted as dates, the > "Date acceptance patterns" should not affect the interpretation of numbers > at all! If the user told it to do so.. again, such M.D pattern simply should not be allowed in a locale that uses the . dot decimal separator, or if it was encountered in the configuration be ignored/discarded. > Is there some separate mechanism for choosing only how an entry you are > currently typing will be interpreted? No. -- You are receiving this mail because: You are the assignee for the bug.
