Skip to content

fix: ensure Continue button text is visible in dark mode (AlertDialog)#11

Merged
dhairyashiil merged 1 commit into
calcom:mainfrom
mrpaaradox:fix/dark-mode-continue-button-text
Feb 21, 2026
Merged

fix: ensure Continue button text is visible in dark mode (AlertDialog)#11
dhairyashiil merged 1 commit into
calcom:mainfrom
mrpaaradox:fix/dark-mode-continue-button-text

Conversation

@mrpaaradox
Copy link
Copy Markdown
Contributor

Summary

  1. Fixes the Continue button label in dark mode so it stays visible in AlertDialogs. In Event Types and Availability, the primary action button was inheriting light text on a light dialog background in dark mode. This adds dark:text-black so the label is readable.

  2. Event Types — Continue button in the “Create event type” AlertDialog
    Availability — Continue button in the “Add schedule” AlertDialog

Before and After

Before:

Screen.Recording.2026-02-21.at.11.57.58.AM.mov

After:

Screen.Recording.2026-02-21.at.12.05.50.PM.mov

Review & Testing Checklist for Human

  • Event Types — In dark mode, open “Create event type” and confirm the Continue button text is clearly visible (dark text on light dialog)
  • Availability — In dark mode, open “Add schedule” and confirm the Continue button text is clearly visible
  • Light mode — Confirm both dialogs still look correct in light mode (no regressions)

Notes

  1. Only styling changes (dark:text-black on the Continue button in two AlertDialogs); no logic or API changes.
  2. Files touched: app/(tabs)/(event-types)/index.tsx, components/screens/AvailabilityListScreen.tsx.

@dhairyashiil

- Event Types: Add dark:text-black to Create event type dialog Continue button
- Availability: Add dark:text-black to Add schedule dialog Continue button

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions github-actions Bot added the mobile Changes to the mobile app (ios/android) label Feb 21, 2026
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Copy link
Copy Markdown
Member

@dhairyashiil dhairyashiil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thank you for the contribution!

@dhairyashiil dhairyashiil merged commit 5309beb into calcom:main Feb 21, 2026
11 of 12 checks passed
devin-ai-integration Bot pushed a commit that referenced this pull request May 23, 2026
- Reject /notify in Telegram groups with DM hint (#3)
- Validate payload fields (title, timeZone, start, end, hosts, attendees) in parseDeliverRequest (#4)
- Wrap deliverNotifications in try/catch, return 422 on formatter crash (#4)
- Add logging across route, service, and delivery modules (#5)
- Add /notify to Slack and Telegram help cards (#7)
- Add error field to DeliverResult for backend retry/unsubscribe decisions (#9)
- Change confirmation message from 'here' to 'via DM' (#10)
- Validate timeZone with Intl.DateTimeFormat before processing (#11)
- Add fallback badge for unknown notificationType (#12)
- Reject /notify in groups with 'check DMs' message (#13)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mobile Changes to the mobile app (ios/android)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants