fix: [DHIS2-16205] Sticky Locked Selector #3516
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…/fix/DHIS-16205_FloatingLockedSelector
…/fix/DHIS-16205_FloatingLockedSelector
|
🚀 Deployed on https://deploy-preview-3516--dhis2-capture.netlify.app |
JoakimSM
changed the title
geethaalwan
approved these changes
Feb 19, 2024
dhis2-bot
added a commit
that referenced
this pull request
Feb 23, 2024
## [100.57.1](v100.57.0...v100.57.1) (2024-02-23) ### Bug Fixes * [DHIS2-16205] Sticky Locked Selector ([#3516](#3516)) ([61158b1](61158b1))
|
🎉 This PR is included in version 100.57.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a sticky top bar class to the ScopeSelector component. Since the
Locked selectoris now sticky, it covers content on the page when we scroll down. This causes theEnrollmentEditEventPageForm.featuretest to fail because the content the test is looking for ends up behind the navbar. After discussion with Eirik and Joakim, I addedclick({ force: true })in line 62 in index.js.