Skip to content

fix: resolve Jump to Top button overlap with DevEx Sessions (#170)#173

Open
mbagalwa wants to merge 1 commit intoIntersectMBO:mainfrom
mbagalwa:fix/170-jump-to-top-overlap
Open

fix: resolve Jump to Top button overlap with DevEx Sessions (#170)#173
mbagalwa wants to merge 1 commit intoIntersectMBO:mainfrom
mbagalwa:fix/170-jump-to-top-overlap

Conversation

@mbagalwa
Copy link
Contributor

Description

Fixes the overlap between the "Jump to Top" and "Meetup" buttons in the bottom-right corner. Uses a responsive layout so both stay visible: on mobile, Jump to Top is above Meetup; on desktop, Jump to Top is to the left of Meetup.

Related to #170

Changes Made

Mobile (< 768px): Jump to Top above Meetup, same right alignment; Meetup at bottom-right.
Desktop (≥ 768px): Jump to Top to the left of Meetup; both on the same baseline.
Files modified: src/MeetupReminderButton/styles.module.css, src/css/custom.css

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Testing

  • I have tested these changes locally
  • I have checked for broken links
  • Code examples have been tested

Checklist

  • My code follows the style guidelines
  • I have performed a self-review
  • I have made corresponding changes to documentation
  • My changes generate no new warnings

@mbagalwa mbagalwa force-pushed the fix/170-jump-to-top-overlap branch from 737d8ff to 814fefb Compare February 26, 2026 16:20
@danbaruka danbaruka self-requested a review March 4, 2026 18:22
Copy link
Member

@danbaruka danbaruka left a comment

Choose a reason for hiding this comment

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

It looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants