-
Notifications
You must be signed in to change notification settings - Fork 134
fix: library dropdowns behavior #2210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
fix: library dropdowns behavior #2210
Conversation
Updated the click event prevention in the BaseCard component to allow dropdown toggle clicks to propagate, ensuring proper coordination between dropdowns.
Replaced the ModalPopup with a Dropdown for better user experience. The filtering dropdowns (publish status/ component type/ tags) all close out if a user clicks anywhere outside of the dropdown menus. In this implementation, however, clicking outside of the opened menu only triggers closing the menu. As in: if a filtering dropdown is open, and decide you want to open a different filtering option, a user has to click twice: once to close the initially opened dropdown, and a second time to open the second filtering option.
Thanks for the pull request, @DanielVZ96! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. Where can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2210 +/- ##
==========================================
+ Coverage 94.15% 94.17% +0.01%
==========================================
Files 1164 1164
Lines 24599 24604 +5
Branches 5381 5367 -14
==========================================
+ Hits 23162 23170 +8
- Misses 1360 1366 +6
+ Partials 77 68 -9 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @DanielVZ96 , this is working great for the main Library page!
We just need the same behavior on the Unit and Section/Subsection pages too.
if (!isDropdownToggle) { | ||
e.stopPropagation(); | ||
} | ||
}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DanielVZ96 Could you apply the same to the section/subsection child preview cards:
And to the Unit child preview cards:
{filterLabels[filter]}{' '} | ||
<Badge variant="light" pill>{publishStatus[filter] ?? 0}</Badge> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, our translated filter labels should be formatted text that includes a variable for this count badge, so that RTL languages can opt to put the count on the left side of the text label. But since that's out of scope for this change it's ok to do as a follow-up PR.
CC @ChrisChV
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice find
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively, this spacing can be handled with CSS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DanielVZ96 I agree with Jill, could you use CSS for the spacing ({' '}
)?
Actually, our translated filter labels should be formatted text that includes a variable for this count badge, so that RTL languages can opt to put the count on the left side of the text label. But since that's out of scope for this change it's ok to do as a follow-up PR.
I will create an issue for this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for those fixes @DanielVZ96 ! I left a couple of nits, but this is working perfectly now.
👍
- I tested this using the PR test instructions
- I read through the code
- I checked for accessibility issues by using my keyboard to navigate
-
Includes documentationN/A - User-facing strings are extracted for translation
{filterLabels[filter]}{' '} | ||
<Badge variant="light" pill>{publishStatus[filter] ?? 0}</Badge> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively, this spacing can be handled with CSS.
onClick={(e) => { | ||
// Wrap the actions in a div to prevent the card from being clicked when the actions are clicked. | ||
const target = e.target as HTMLElement; | ||
const isDropdownToggle = target.closest('[data-testid="dropdown"], [data-testid="container-card-menu-toggle"], .pgn__dropdown-toggle-iconbutton'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not comfortable with testid
attributes being used in running code -- and they're even a last resort when identifying elements in tests. Can we use classes here instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And is there any way to avoid duplicating this logic every time we need it? E.g using a utility function, or at least only declaring the function once per file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh you are absolutely right! i refactored it into a function in each file. i couldn't find any place to put it as a shared utility function tbh.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much better with those changes, thank you @DanielVZ96 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DanielVZ96 Is it possible to fix this without opening the sidebar when clicking the card menu (without selecting the card)? If it is not possible, could you ask Product to see if that behavior is correct (somewhere I remember reading that it is not)?
{filterLabels[filter]}{' '} | ||
<Badge variant="light" pill>{publishStatus[filter] ?? 0}</Badge> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DanielVZ96 I agree with Jill, could you use CSS for the spacing ({' '}
)?
Actually, our translated filter labels should be formatted text that includes a variable for this count badge, so that RTL languages can opt to put the count on the left side of the text label. But since that's out of scope for this change it's ok to do as a follow-up PR.
I will create an issue for this
@edschema should we prevent the sidebar change/opening? here's a video that shows the sidebar opening when a card menu toggle is clicked. Grabacion.de.pantalla.2025-06-27.a.la.s.8.37.58.p.m.mov |
Hi @DanielVZ96! This is our mistake: we should have created a ticket for this behavior. I apologize. Clicking overflow menu should not select the card, and correspondingly should not open the sidebar for that object. If the user clicks either "Edit" or "add to collection" the sidebar should open. "Edit" opens the sidebar behind the edit modal. "Add to collection" should open the "manage" tab on the sidebar in the add to collection mode. For container blocks, there is "open" so sidebar behavior does not apply since opening navigates to the container's page. In unit views, the same pattern should persist. "edit" opens the sidebar behind the edit modal for component, "add to collection" opens the manage sidebar in edit mode. For other container pages, Section/Subsection, should follow similar rules. "Open" navigates to a new page, so not relevant, "add to collection" shifts to a new collection. |
Description
Changes:
SearchFilterWidget
to useDropdown
component instead ofModalPopup
in order to be able to close the current filter and interact with other elements in a single click.BaseCard
component to allow proper event propagationSupporting information
Testing instructions
On a library v2:
Open any of the following filters: type, publish status, tags
Open another filter
Assert only a single click is needed to close and open a new filter
Create multiple library units, sections/subsections, collections, components
Open the dropdown menu of each one of them as shown in the picture