After blur on the custom text field the date format should update below.

[dilipbheda]

When I click on any radio button of date format, Date format updates below the list of the radio button. It's working perfectly.

Now, When I click on the custom option of the date format and enter the PHP date format in the text field then the field doesn't update their format below the radio button unless when I click on any radio button. This is not user-friendly.

Ideally, it should be updated when the blur in the custom text field.

I have updated time format too.

I have attached an image for better understanding.

[dilipbheda]

Attached Image.

[dilipbheda]

Updated patch for this.

[afercia]

@dilipbheda thanks for your report.

Ideally, it should be updated when the blur in the custom text field.

For me, it updates on blur. Clicking on any blank part of the page (and thus blurring the field) updates the preview, and tabbing away from the field when using the keyboard update the preview as well. If it doesn't work for you, maybe there's something else causing conflicts? Does it still happen with all plugins disabled and a default theme activated?

Worth noting using keyup as in your proposed patch would not work when pasting a value with the mouse right click.

[Girishpanchal]

@afercia

Yes, I think @dilipbheda has suggested that the preview should be updated on keyup as saw their patch. But he has written that it should be updated on blur in the custom field. I have also checked with default theme without using any plugin and it works with blur, tabbing away from the field and click on any blank part of the page.

Here is the update patch with keyup and input

This patch works for both on paste and on mouse right click paste.

[Girishpanchal]

Updated with keyup and input.

[afercia]

For some background, see the original ticket and changeset: #12636 / [15757].

@Girishpanchal thanks. I'd agree input seems a better option, worth trying it now that WordPress has dropped support for old IE versions that don't support input. However, firing an AJAX request at any key press is something that should be avoided. With the proposed patch:

• keyup will fire an AJAX request at any key press, including non-character keys like the arrow keys, Home, End, etc. I think keyup shouldn't be used, unless I'm missing something.
• input will cover any input with both mouse and keyboard; however, I'd say nothing should happen while users are still typing; ideally, the AJAX request should be debounced while users are still typing in the field and fire only when they stop typing. WordPress is already using this pattern in other places, for example for the Themes and Plugins search, and I'd suggest to use the same pattern here too.

[Girishpanchal]

@afercia

I have updated patch according to your suggestion. I have added only input and remove the keyup which fire an AJAX request on any key press.

I have used SetTimeout.

Thank you.

[Girishpanchal]

Updated patch with SetTimeout and removed keyup.

[afercia]

The patch looks good to me. It just needs some adjustments to spacings. I'd also recommend to decrease the interval from 800 to 500. WordPress is already using 500 in a few places in the admin, for example for some search fields using underscore .debounce(). See also a similar setTimeout() implementation for the "insert link" search:
https://core.trac.wordpress.org/browser/trunk/src/wp-includes/js/wplink.js?rev=42807#L72

[Girishpanchal]

Updated spacing issues and interval time.

[Girishpanchal]

@afercia ,

I have updated patch according to as you suggested.

Thank you.

[afercia]

Discussed during today's accessibility bug-scrub an agreed we'd like to propose this for 4.9.9 consideration.

[audrasjb]

Hi, 5.0.3 is going to be released in a couple of weeks. We are currently sorting the remaining tickets in the milestone.

This ticket is triaged in milestone 5.0.3. Now it will needs commit and backport to the related branch. Adding dev-feedback keywords to see if it can land in 5.0.3 at the very beginning of January.

[desrosj]

Going to punt this to 5.1 since it is not block editor related, a regression, or a major bug fix.

[afercia]

Unfortunately we're running out of time for 5.1, sorry. This ticket does have a patch though, probably needs just a refresh. Punting to 5.2.

[afercia]

43364.diff​ refreshes the patch.

[afercia]

43364.2.diff​ improves coding standards.

[afercia]

In 44758:

Accessibility: General Settings: Update custom date/time format previews while typing.

The custom date/time format previews in General Settings were updated only when blurring the related input fields. With this change, they're now updated when users finish typing a custom format, properly debouncing the input event callback.

Props dilipbheda, Girishpanchal.
Fixes #43364.