Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing the year of a publication date is not efficient (too many clicks) #9947

Closed
benoitchantre opened this issue Sep 17, 2018 · 1 comment
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Enhancement A suggestion for improvement.

Comments

@benoitchantre
Copy link
Contributor

benoitchantre commented Sep 17, 2018

Describe the bug
The datepicker only allows us to browse month by month. This works in a standard workflow, but it is not practical when you need to change the value by 2-3 years or more. It happens sometimes when you need to reorganize the content. The Classic editor allows us to do that easily.

Example of use case : your website has a "Press review" page and you decide to reorganize these press reviews as individual posts in a press review category.

Current workaround: use the quick edit panel.

To Reproduce
Steps to reproduce the behavior:

  1. Open an existing post or page
  2. Click on the publication date
  3. Try to change the date 3 years ago
  4. Count how many clicks in need

Expected behavior
Ability to enter the year manually for a quick change.

Tested in Gutenberg 3.8

@designsimply
Copy link
Member

Thank you for writing in! This is being worked on as a part of #1311, so I will close this issue as a duplicate and it will be noted there.

@designsimply designsimply added [Type] Enhancement A suggestion for improvement. [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed labels Sep 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

2 participants