The calendar block having issue with today date.

[viralsampat-multidots]

What problem does this address?

Hello Team,

I have worked with Gutenberg block and I have found the "Calendar" block having issue with today's date. The today's date is not highlighting, We can't assume which is today's once.

So, it should be highlighted, So user can easily knowing the today's date.

Here, I have taken screenshots to better understand.

Issue:

What is your proposed solution?

I think that the today's date should be highlighted.

Expected

Here, I have attached screenshot for expected result.

Thanks,

[himanshupathak95]

Hey @viralsampat-multidots, Thanks for bringing this up.

I tested the same, and it works fine for me both in the editor and front end. The "today's date" is highlighted correctly for me, although I do believe the highlight can be made more accessible.

Editor -

Frontend -

I noticed the highlight is different for different themes, perhaps you could provide more information on the environment and theme for reproduction.

[viralsampat-multidots]

Hello @himanshupathak95

Thank you so much for the detail feedback.

Let me check it from my end, Also, I will provide all the environmental information in detail.

Thanks,

[benazeer-ben]

I was able to reproduce this issue in the Twenty Twenty-Five, Twenty Twenty-Four, and Twenty Twenty-Three themes.

Please see the attached screenshot for reference.

Instead of relying on the theme's styles, it would be better to add the necessary styles directly to the Calendar block to ensure today's date is consistently highlighted across all themes.

Screenshare.-.2025-01-02.12_35_04.PM.mp4

[hanneslsm]

Instead of relying on the theme's styles, it would be better to add the necessary styles directly to the Calendar block to ensure today's date is consistently highlighted across all themes.

I wholeheartedly disagree. Styling is the essence of themes, so we should rely on it.
Some basic stylings come with the block editor as fallbacks and that's fine. The CSS specificity must be very low though, so that everyone can overwrite the styles. Best would be that every implemented fallback style would be also possible to change within the editor, not only CSS.

Highlighting the todays date as in this issue / the pull requests is in my opinion not the way to got. On the other hand, giving theme creators and users the possibility to highlight the date is.

[hanneslsm]

(Site note: The title of the issue can be more specific and like a enhancement suggestion, e.g. Calendar: Add styling to highlight todays date.)

[t-hamano]

Thanks for the suggestion.

Both PRs #68458 and #68460 try to solve the problem by applying an underline to today's date, but I think this approach is unacceptable for the following reasons:

• In the Calendar block, any date with posts becomes a link, meaning that it is underlined by default. If today's date is always underlined, it becomes impossible to distinguish whether there are posts published today or not.
• Underlining gives the wrong impression that the text is clickable. For similar reasons, the underline inline format was removed from the dropdown (see this discussion).

In this sense, we need to highlight in a different way. Some people may think that making the text bold is enough. Others may want to apply a background color or change the text color.

It is possible to build a UI that achieves all of this, but it will bloat the UI.

Given these, I think highlighting today's date is an "advanced setting" and does not necessarily require a UI.

For example, you can highlight today's date via theme.json:

{
	"styles": {
		"blocks": {
			"core/calendar": {
				"css": "& #today { background: #ccc; }"
			}
		}
	}
}

Or, write the following CSS to the calendar block via the global styles > blocks > Calendar > Advanced Additional CSS:

& #today {
  background: #ccc;
}

This statement will be expanded as follows:

:root :where(.wp-block-calendar #today){
  background: #ccc;
}

[t-hamano]

I suggest closing this issue as "won't fix". What do you think?

[t-hamano]

For now, let's close this issue and the associated PR, we can reopen it if we find a better approach.