Replace foundation dropdowns with popovers#3541
Conversation
Test results 27 files 27 suites 44m 50s ⏱️ Results for commit 4af148b. ♻️ This comment has been updated with latest results. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3541 +/- ##
=======================================
Coverage 62.09% 62.09%
=======================================
Files 611 611
Lines 44865 44865
Branches 43 43
=======================================
Hits 27861 27861
Misses 16994 16994
Partials 10 10 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
b40e9fb to
89450e1
Compare
adb7679 to
821c9ba
Compare
johannaengland
left a comment
There was a problem hiding this comment.
I don't really like the alignment of the dashboard settings popover - is it possible to get it closer to how it was before?
@johannaengland I have created a PR which adds support for aligning the popover on multiple sides, #3550. When this is merged, I can rebase and place the dashboard settings popover on the left. Can also move the Edit Token dropdown to the top side. |
821c9ba to
4af148b
Compare
The PR has been rebased, and the Dropdown Settings is positioned on the left of the settings button. The "Confirm delete token" modals have been positioned on top. I also updated the screenshots and descriptions in the table to match the current state. |
4af148b to
dd7a63f
Compare
|



Scope and purpose
Resolves #3531. This PR replaces remaining dropdowns in the codebase with the new Popover component.
The following tools have been updated to use the new Popover:
This pull request
Screenshots
Aligned on the bottom instead of on the left side, as new popover does not yet support this.Aligned on the left, with the new popover styles.Popover was aligned to the bottom instead of the top, to make it consistent with other delete dropdowns.Aligned on the top, using the new popover styles. Used in both/useradmin/tokens/editand/useradmin/jwt_tokens/editContributor Checklist
Every pull request should have this checklist filled out, no matter how small it is.
More information about contributing to NAV can be found in the
Hacker's guide to NAV.
<major>.<minor>.x). For a new feature or other additions, it should be based onmaster.