Skip to content

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

Open
wants to merge 14 commits into
base: master
Choose a base branch
from

Conversation

DanielVZ96
Copy link
Contributor

Description

Changes:

  • Refactored SearchFilterWidget to use Dropdown component instead of ModalPopup in order to be able to close the current filter and interact with other elements in a single click.
  • Fixed dropdown coordination in BaseCard component to allow proper event propagation
  • Minor spacing adjustment in filter by published

Supporting 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

image
  • Assert that each time you open a new dropdown, the previous open one is closed.

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.
@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Jun 22, 2025
@openedx-webhooks
Copy link

openedx-webhooks commented Jun 22, 2025

Thanks for the pull request, @DanielVZ96!

This repository is currently maintained by @bradenmacdonald.

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 approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To 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:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If 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:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@DanielVZ96 DanielVZ96 marked this pull request as draft June 24, 2025 10:09
@DanielVZ96 DanielVZ96 marked this pull request as ready for review June 24, 2025 11:06
Copy link

codecov bot commented Jun 24, 2025

Codecov Report

Attention: Patch coverage is 80.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 94.14%. Comparing base (962b30b) to head (6dbd7a8).
Report is 9 commits behind head on master.

Files with missing lines Patch % Lines
src/library-authoring/units/LibraryUnitBlocks.tsx 60.00% 6 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2210      +/-   ##
==========================================
+ Coverage   94.11%   94.14%   +0.02%     
==========================================
  Files        1164     1164              
  Lines       24507    24616     +109     
  Branches     5201     5255      +54     
==========================================
+ Hits        23065    23174     +109     
  Misses       1374     1374              
  Partials       68       68              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@DanielVZ96 DanielVZ96 requested a review from pomegranited June 24, 2025 16:53
Copy link
Contributor

@pomegranited pomegranited left a 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();
}
}}
Copy link
Contributor

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:

image

And to the Unit child preview cards:

image

Comment on lines +65 to 66
{filterLabels[filter]}{' '}
<Badge variant="light" pill>{publishStatus[filter] ?? 0}</Badge>
Copy link
Contributor

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

nice find

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open-source-contribution PR author is not from Axim or 2U
Projects
Status: Needs Triage
Development

Successfully merging this pull request may close these issues.

3 participants