-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature/555 add cyan to overview #872
Conversation
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'm seeing some rendering issues with the ResizeObserver
. On smaller screens (1000px X 720px) a scrollbar is shown for the accordion headers. Also, I'm seeing a lot of flickering (gif below) on smaller screens (1000px X 720px). It seems like removing , overflowX: 'hidden'
from line 120 of VirtualizedList.tsx
fixes the issue.
What was the issue the ResizeObserver
is intended to fix? I'm assuming it is just to move away from reach-ui.
An unrelated issue, the pageYOffset
(used on line 89 of the VirtualizedList.tsx
file) value has been deprecated. We should switch to scrollY
.
The It looks like Good catch on that overflow issue, I'll make those changes. |
Kudos, SonarCloud Quality Gate passed!
|
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.
Thank you for making those changes. The switch to using ResizeObserver
makes sense.
I'm going to go ahead and merge this in. Kiki can let us know what she thinks of the new HABs text during our next meeting.
Related Issues:
Main Changes:
ResizeObserver
to theVirtualizedList
component to address rows with dynamically-sized content.ResizeObserver
in the app. This is due to the rate at which elements in the virtualized list are added to the observation list: the errors are triggered whenResizeObserver
sends multiple messages inside a single animation frame, fearing an infinite loop, which is not the case here. As stated by the author (https://stackoverflow.com/questions/49384120/resizeobserver-loop-limit-exceeded#comment86691361_49384120 and ResizeObserver#observe() firing the callback immediately results in infinite loop WICG/resize-observer#38), this error is usually benign and can be ignored.Steps To Test:
TODO: