[wp-trac] [WordPress Trac] #38342: Quick Draft: Leverage REST API endpoints

WordPress Trac noreply at wordpress.org
Thu Nov 24 22:43:40 UTC 2016


#38342: Quick Draft: Leverage REST API endpoints
-------------------------------------+-------------------------------------
 Reporter:  adamsilverstein          |       Owner:  joehoyle
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  Future Release
Component:  Administration           |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch 4.8-early      |     Focuses:  accessibility,
  needs-unit-tests needs-refresh     |  javascript, rest-api
-------------------------------------+-------------------------------------
Changes (by afercia):

 * keywords:  has-patch 4.8-early needs-unit-tests => has-patch 4.8-early
     needs-unit-tests needs-refresh


Comment:

 Couple more issues.

 1
 I'm not sure the locale in `Intl.DateTimeFormat` can be left to
 `undefined`. I live in Italy, but I keep my operating system and browsers
 in English. Seems there are inconsistencies across browsers, see the
 screenshot below.

 [[Image(https://cldup.com/6IGfEVZaln.jpg)]]

 Notice the OS default language is set to a "generic" English (no en-GB or
 en-US) and Chrome on the left displays an en-GB date format while Firefox
 on the right an en-US one. I have to manually change my OS language to en-
 US to get the same behaviour in both browsers. Besides the inconsistency,
 seems setting the locale to `undefined` makes the date format dependent on
 the OS language, at least on macOS. This may vary on other platforms.

 By the way, the main issue is that I've set the admin UI in French :)
 Regardless of the OS or browser language, the date should be displayed in
 the format of the language set in the user profile.

 2
 When quickly clicking twice the "Save Draft" button, I get two new drafts.
 While the list below the form shows just one new draft, on the Posts >
 Drafts screen I have two new ones. This is probably because the button
 doesn't get disabled when submitting the form as in the previous AJAX
 implementation.
 Note: when the form gets re-rendered, focus should be moved to the title
 field.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38342#comment:75>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list