-
Notifications
You must be signed in to change notification settings - Fork 36
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
DOP-4815 #1163
Conversation
This reverts commit cd81024.
this does not address the issue highlighted by the original description in DOP-4805 (due to tabs not appearing on first render and pushing content down). since we are reading from local storage to preserve tabbed content space back, may have to put the effect of scrolling back |
After some investigation, found out that the tabs update is possibly causing this issue. The content is hidden in tabs, and even though the content is available in HTML, its being hidden and thus the browser sometimes can find this and scroll down. to mitigate this, added the useEffect back, but with updated method of calculation and calculates within the timeout, not before |
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.
Thanks for working on this. I noticed some weird stuttering when attempting to permalink to a heading for the first time. I don't see this happening on prod though. Just wanted to flag this in case this is not something we want to keep.
Screen.Recording.2024-07-12.at.2.25.29.PM.mov
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.
thanks for catching this! actually went ahead and removed the scroll position calculation, and instead went with elm.scrollIntoView (which should act the same each time) 👍 |
i believe this is due to the footer being lazy loaded in my staging! (browser attempts to scroll to the note at top of page, except theres no footer) that said, the point of that link was to follow the link in the note! i updated the description PTAL |
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.
Looks great, thank you for jumping on this
Stories/Links:
DOP-4815
DOP-4805
Current Behavior:
Glossary component with anchor tag in link is hidden
DOP-4805 Scrolling to top when linking to table
DOP-4805 original slack thread shows link in note not going to right location for Target component (click link in note to be falsely led. this was the slack thread in DOP-4805)
Staging Links:
Glossary component link
DOP-4805 Removed scrolling to top
DOP-4805 scroll position is updated for Target component (link in note leads you to correct section)
Notes:
README updates