Skip to content

Comments

TMS-1158: Remove micromodal close attribute from mobile-nav container#543

Merged
eebbi merged 3 commits intomasterfrom
TMS-1158
Aug 13, 2025
Merged

TMS-1158: Remove micromodal close attribute from mobile-nav container#543
eebbi merged 3 commits intomasterfrom
TMS-1158

Conversation

@eebbi
Copy link
Contributor

@eebbi eebbi commented Aug 13, 2025

Severa-ID: 2247
Severa-kuvaus: TMS-1158 Saavutettavuus: Päävalikon ja lomakkeen responsiivisuus
Task: https://hiondigital.atlassian.net/browse/TMS-1158

Description

Remove modal close attribute to prevent mobile nav closing when the user taps on the container when attempting to scroll down

Types of changes

  • 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 change)

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @eebbi, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a bug where the mobile navigation would unexpectedly close when users attempted to scroll within its container. The fix involves removing a specific attribute that was causing the modal to close upon interaction with the container, thereby improving the user experience and accessibility of the mobile navigation.

Highlights

  • Mobile Navigation Fix: Addresses an issue where the mobile navigation would close prematurely when users attempted to scroll within its container.
  • Accessibility Improvement: Enhances user experience by preventing unintended closure of the mobile navigation, making it more usable, especially on touch devices.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request correctly fixes a usability issue on the mobile navigation where tapping to scroll would inadvertently close it. The change is simple and effective, removing the data-micromodal-close attribute from the overlay. I have one minor suggestion to improve the clarity of the changelog entry.


## [Unreleased]

- TMS-1158: Disable mobile-nav from closing when scrolling by clicking the inner container

Choose a reason for hiding this comment

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

medium

For improved clarity in the changelog, this entry could be rephrased to more accurately reflect the code change. The fix removes the close trigger from the overlay container to prevent the navigation from closing when a user taps the screen to scroll.

- TMS-1158: Prevent mobile-nav from closing when tapping the overlay to scroll.

@eebbi eebbi merged commit 3c2bee8 into master Aug 13, 2025
2 of 4 checks passed
@eebbi eebbi deleted the TMS-1158 branch August 13, 2025 16:07
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.

1 participant