-
Notifications
You must be signed in to change notification settings - Fork 223
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
EDSC-4252: Update the Application header to match the design in post tophat2 update #1816
Conversation
89cfca7
to
579299b
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1816 +/- ##
==========================================
- Coverage 93.46% 91.02% -2.44%
==========================================
Files 772 770 -2
Lines 18555 18565 +10
Branches 4784 4788 +4
==========================================
- Hits 17342 16899 -443
- Misses 1165 1524 +359
- Partials 48 142 +94 ☔ View full report in Codecov by Sentry. |
919464f
to
dfa6f01
Compare
@@ -21,4 +17,14 @@ $headerHeight: 2rem; | |||
.is-panels-dragging & { | |||
pointer-events: none; | |||
} | |||
|
|||
&__color-map { |
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.
This might be OBE
// map tools. | ||
return routeWrapperWidth - 55 | ||
// Set the maxWidth to the available space minus the width of the secondary toolbar with some buffer. | ||
const secondaryToolbarWidth = document.querySelector('.secondary-toolbar').offsetWidth |
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.
This is getting tested by playwright panels.spec.js
static/src/js/components/SecondaryToolbar/SecondaryToolbar.scss
Outdated
Show resolved
Hide resolved
… for borders around the ma
…acement, and scale-control placement - Revert banner to HEAD of main
…that fails on GH actions
fa9b961
to
f8fb9fb
Compare
046498c
to
c30a49a
Compare
@@ -103,6 +103,7 @@ const SearchTour = () => { | |||
stepIndex={stepIndex} | |||
continuous | |||
callback={handleJoyrideCallback} | |||
disableScrollParentFix |
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.
https://docs.react-joyride.com/props - this was to fix an issue for some cases on joyride in our case with the wrapping-container this was adding a style that messed up the overflows we added in SCSS
it was adding overflow: initial
to the parent element of the Search Tour
…ger needs logic, fix state for initial project value
@@ -22,7 +22,7 @@ export const NotFound = ({ | |||
|
|||
// Modify the background color of root element for the not found page so we can load stars jpg | |||
const selectElementById = () => { | |||
const element = document.getElementById('app') | |||
const element = document.getElementById('wrapping-container') |
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.
This is needed because we can't set this to black with the map selector unless we add a list of all the routes etc. Since this is the route we will be going to if it matches none of our routes
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.
This is interesting. Not a deal breaker but Id be curious to see if react-router had a way to check to see if any routes were matched on the current page.
This reverts commit cf03ea6.
@@ -22,7 +22,7 @@ export const NotFound = ({ | |||
|
|||
// Modify the background color of root element for the not found page so we can load stars jpg | |||
const selectElementById = () => { | |||
const element = document.getElementById('app') | |||
const element = document.getElementById('wrapping-container') |
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.
This is interesting. Not a deal breaker but Id be curious to see if react-router had a way to check to see if any routes were matched on the current page.
// Set the maxWidth to the available space minus the width of the | ||
// map tools. | ||
return routeWrapperWidth - 55 | ||
return routeWrapperWidth - 165 |
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.
Maybe add back a comment here so we know why were subtracting. Something simple like this would probably work.
Subtracting from the available space to ensure the user menu/login button and map tools remain visible at the maximum panel width
@@ -87,6 +89,7 @@ class SecondaryToolbar extends Component { | |||
onUpdateProjectName(newProjectName) | |||
} | |||
|
|||
// Needed for Save Project so page does not change |
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 think you could elaborate here. Not sure exactly what you mean by this comment. Ideally were using full sentences and adding all the required details to understand the implementation more easily.
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.
Updated. we discussed this at one point as a team if we needed some of the event.stopPropagation()
calls but, we do because if we don't have that when the project-id updates the url path it tries to refresh the page. (If you remove them I mean)
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.
The spacing here looks a little wonky when a colormap is visible. If possible, it would be great if there was the same about of space between the map tools and colormap as there is between the colormap and scale
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.
The only issue with that is that is really going to break a significant amount of the map.spec tests
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.
The inconsistent spacing looks pretty bad. If we cant get it in now, we should write an improvement ticket to track it.
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've added those to the https://bugs.earthdata.nasa.gov/browse/EDSC-4302 ticket as new AC with the comment in the description
static/src/js/containers/WrappingContainer/WrappingContainer.jsx
Outdated
Show resolved
Hide resolved
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.
One last tweak 😄
@@ -15,12 +15,14 @@ export const WrappingContainer = (props) => { | |||
const { search, pathname } = location | |||
let isMapPage = ['/search'] | |||
|
|||
// Currently saved projects and a project page share route1 | |||
// Currently saved projects and a project page share route as such we must determine if we are on the saved projects page |
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.
Currently saved projects and a project page share a route as such we must determine if we are on the saved projects page
😄
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.
that's what I get for going fast 🤦
Overview
What is the feature?
Integrating tophat2's new features onto earthdata search to deprecate the additional header. Implementing design to move secondary toolbar buttons as an overlay on each applicable page
What is the Solution?
Removing the Application header creating floating buttons for the secondary toolbar onto the map
What areas of the application does this impact?
Changes the app header, locations of colormap and legend, updates the secondary toolbar that appears on most application pages
Testing
Reproduction steps
Attachments
When Error Banner is up
When Colormap is up
Toplevel page:
Preferences but, looks the same on all the pages
Order Status page:
Project page:
My project saved project
Not found page:
Logged out:
These buttons do in fact line-up
The order status page:
Checklist