'Current date' default for date only field can be off depending on time zone setting

Updated IS with steps to reproduce. I suspect this may have something to do with the 'Date only' getting a time set of 12:00?

This I believe is as per expected behaviour as can be seen in the following documents in core/modules/datetime/src/DateTimeComputed.php file.

// If the format did not include an explicit time portion, then the
// time will be set from the current time instead. For consistency, we
// set the time to 12:00:00 UTC for date-only fields. This is used so
// that the local date portion is the same, across nearly all time
// zones.
// @see \Drupal\Component\Datetime\DateTimePlus::setDefaultDateTime()
// @see http://php.net/manual/datetime.createfromformat.php

and this link
https://www.php.net/manual/en/datetime.createfromformat.php#110385

Thanks @pameeela & @adityasingh you have it rightly pointed, the issue is because by default time is set to 12:00:00

File: core/lib/Drupal/Component/Datetime/DateTimePlus.php
@line: 711

 /**
   * Sets the default time for an object built from date-only data.
   *
   * The default time for a date without time can be anything, so long as it is
   * consistently applied. If we use noon, dates in most timezones will have the
   * same value for in both the local timezone and UTC.
   */
  public function setDefaultDateTime() {
    $this->dateTimeObject->setTime(12, 0, 0);
  }

This is actually causing the issue to occur for few hours as long the date differs between local time zone (if other that UTC) and UTC.

One possible solution might be to adjust the default fallback time according to sites local time zone i.e get +/- in time from UTC time for current timezone and accordingly set the default time for the date field.

Feel free to share suggestions.

Mistakenly had it closed...

Just ran into this one myself. It seems the most logical solution to me would be to set the datetime created to midnight in the current timezone. What is the point of standardising the time portion when it makes the date portion incorrect, and that's the only portion we actually care about.

It's hard to see how this buggy behaviour could be considered "works as designed".

In case of the 'Date only' setting the 'UTC' is used instead of user's timezone. It looks like this is the reason of the issue.

Duplicate of #2993165: Date Only field shows incorrect default value when UTC date is different than user's date and that was created earlier and has more activity, so closing this one.

@pameeela, Is it make sense to transfer the patch from this issue there? It seems is different from those offered in that issue.

@wombatbuddy, yes that's a good idea, a new patch might just revive the issue :) It is failing though, not sure whether the fails are random or not, but if not would be good to address them before you transfer it. Thanks!