Event time on monthly view is cut short

Functie
1

Event times show as 11a and 3p, instead of 11am and 3pm:

Screenshot 2025-11-07 at 11.54.31

The issue seems to come from the provided data:

Screenshot 2025-11-07 at 11.57.33

1 like
2

Moving this to feature and would like some tips from @lindsey

The fix here is pretty trivial:

diff --git a/plugins/discourse-calendar/assets/javascripts/discourse/components/full-calendar.gjs b/plugins/discourse-calendar/assets/javascripts/discourse/components/full-calendar.gjs
index 79940a66ba..22b9306052 100644
--- a/plugins/discourse-calendar/assets/javascripts/discourse/components/full-calendar.gjs
+++ b/plugins/discourse-calendar/assets/javascripts/discourse/components/full-calendar.gjs
@@ -79,6 +79,11 @@ export default class FullCalendar extends Component {
       timeZone: this.currentUser?.user_option?.timezone || "local",
       firstDay: this.firstDayOfWeek,
       displayEventTime: true,
+      eventTimeFormat: {
+        hour: "numeric",
+        minute: "2-digit",
+        meridiem: "short",
+      },
       weekends: this.args.weekends ?? true,
       initialDate: this.args.initialDate,
       height: this.args.height ?? "100%",

But full calendar is deliberate about conserving space with meridiem narrow

Can we afford the extra space here? Is it worth it?

2 likes
4

The impact on space is pretty minimal either way — either we are slightly shortening the time or we are slightly shortening the event title.

am / pm and a / p are equally clear to me in this context. Are we finding that members are confused about this?

2 likes