-
Notifications
You must be signed in to change notification settings - Fork 6
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
GHG -> main #679
GHG -> main #679
Conversation
Handles issue in #682 (comment) While putting this fix, I noticed that `use-media-query` returns document body size, which differs from how CSS media query works. This results in a weird style in between 991 px ~ 1000 px. (screenshot attached, it is on ghg.center now) 👉 I didn't fix this problem, but I patched it with CSS. (Eventually, we would need to move to Container query instead of media query: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) ![Screen Shot 2023-10-04 at 3 01 10 PM](https://github.com/NASA-IMPACT/veda-ui/assets/4583806/215d0515-e4ff-4b42-b0b1-63a21506ad1c)
The date gets set back when I try to change the date for Plume datasets: https://ghg-demo.netlify.app/data-catalog/emit-ch4plume-v1/explore?projection=mercator%7C%7C&basemapid=satellite&datetime=2023-07-29T10%3A06%3A30.000Z This is because when a user inputs the date, the code checks if the date is in datetime list of the collection. Since Dashboard only provides daily level selection, selected datetime gets rounded down to the midnight of the selected date. Plume data datetimes don't have 00:00 timestamps, the selected date gets invalidated. I changed the code to check only day-level equality to align with dashboard capacity.
fix the bug where we pass `initialPosition` prop even when there is none defined by an editor.
Co-authored-by: Erik Escoffier <[email protected]>
Follow up of : #691 Fixing panel overflowing problem in https://deploy-preview-201--ghg-demo.netlify.app/data-catalog/epa-ch4emission-yeargrid-v2express/explore?projection=equirectangular%7C%7C&basemapid=light&datetime=2020-01-01T00%3A00%3A00.000Z Wow Scroll is hard. It will be ideal if we can find a way to stick the date widget and make only layers roll, but I am giving up here.. This change basically resurrects what `ShadowScroll` does for HTML and CSS sans some unnecessary elements for this case. I noticed that the window scroll sometimes pops up if you scroll very fast on the panel area. (Sorry, I cannot reproduce stably enough to grab a screen recording.) this error happens in production environment, too, so this PR doesn't necessarily introduce the error. But with the default (thicker) scroll, the error seems more noticeable.
Follow up of #692 Currently panel body is showing up scrolls even when not needed. This PR fixes the issue.
Handles one of warnings in #693
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 pushed a commit with some css fixes. Mostly it rounds the button corners on the analysis page given that it was clashing with the remaining buttons on the same page. If the idea is to move to square buttons, then a overall change is required.
I'd like to us to understand if the ShadowScrollbar really is a source of problems and performance issues, given that it adds a shinier finish to the app.
Without it, the dropdowns look a bit like an afterthought.
Besides this I didn't see anything that would be GHG specific.
That is a good point about how the dropdown looks, so I added |
@hanbyul-here My comment was related to styling, rather than behavior. Unfortunately there's no other way to style a scrolling element besides javascript. In this case we also want the shadow indicating that there's scrollable content which is not doable with css alone. |
As far as I can read, ShadowScrollbar attaches extra html to generate the shadow gradient in the background. If we think it is necessary, we can still make that effect with additional markup and styles, at least for the ones that will likely have scrolls. It won't be as sleek as the ShadowScroll, but there are some ways that we can style scrolls so they look like more thoughts went into them. (I made the style change, then I thought it was better to apply it more globally, so I reverted the style.) But all in all, you agree that the visual degradation is acceptable, then can you clarify what changes you are requesting? |
I just wanted us to understand if ShadowScrollbar really is the culprit behind the errors that we were seeing and why that was happening. However I do understand that there may not be time to track down this error, and this (together with removing the redirects), seems to solve the problem. I'll leave this to your decision. |
I will merge this, and still have a discussion about how we can improve style of scroll. nudging @faustoperez |
This PR, merged to
ghg
Features
/collections
metadata (spatial, temporal extent)Bugfixes
Copy changes
Other PRs, merged to
main
Added in veda UI but made configurable (so not affecting veda-config):
Bugfixes