Make WordPress Core

Opened 3 years ago

Closed 3 months ago

#54784 closed defect (bug) (reported-upstream)

Scheduled post calendar missing has-events dot

Reported by: cometgrrl's profile cometgrrl Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.8.3
Component: Editor Keywords:
Focuses: ui Cc:

Description

Quick summary

When scheduling a post or page for later publishing, you're presented with a calendar dialog to select the post's publish date. If there are other posts scheduled to publish on a given day, a small "dot" is displayed beneath that date (displayed with the CSS class has-events).

If you schedule a post/page to publish on February 28/29th or March 1st, this dot doesn't appear.

Steps to reproduce

  • Create a new post.

Schedule the post to publish on February 28, 2022 (at any time), February 29, 2024 (at any time), or March 1, 2022 at midnight (0:00 AM). Click "Schedule" to save the post.

  • Create a second new post.
  • Open the scheduling dialog and navigate to the first post's scheduled month.

Expected Results

A small "dot" should appear on the first post's scheduled date to notify you that a post is scheduled for that date. This happens for every other date I tested other than February 28th/29th (at any time) or March 1st (specifically at midnight).

Actual Results

No dot is shown.

Attachments (1)

146685168-2f1d246e-710d-4a4c-bb7b-703600e9e255.png (15.1 KB) - added by cometgrrl 3 years ago.
screenshot

Download all attachments as: .zip

Change History (2)

#1 @sabernhardt
3 months ago

  • Component changed from General to Editor
  • Milestone Awaiting Review deleted
  • Resolution set to reported-upstream
  • Status changed from new to closed

Sorry for the late reply.

A similar issue was opened on the Gutenberg repository, and it seemed to be fixed:
https://github.com/WordPress/gutenberg/issues/48616

I'll close this as reported-upstream. If you still experience the missing dot, please comment on that issue and/or create a new issue in the Gutenberg repository.

Note: See TracTickets for help on using tickets.