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
Bug 1906899: fix offset in quick start highlight bounding box #7475
Bug 1906899: fix offset in quick start highlight bounding box #7475
Conversation
a997a10
to
c8ad328
Compare
/test e2e-gcp-console |
@christianvogt: This pull request references Bugzilla bug 1906899, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@christianvogt: This pull request references Bugzilla bug 1906899, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
/lgtm
One nit, doesn't make a difference if it's left.
|
||
const LAST_PERSPECTIVE_USER_SETTINGS_KEY = 'console.lastPerspective'; | ||
|
||
export const useValuesForPerspectiveContext = (): [ |
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.
export const useValuesForPerspectiveContext = (): [ | |
default export (): [ |
Named files should default export. Generic files utils...
can export multiple/named.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewballantyne, christianvogt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@christianvogt: All pull requests linked via external trackers have merged: Bugzilla bug 1906899 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes:
https://issues.redhat.com/browse/ODC-5234
Analysis / Root cause:
The bounding box of the target node to highlight gets calculated immediately after the highlight is rendered to the page. However, this occurs before popper has positioned the highlight. Since the Popper component rendered the content without any positional information, it ended up rendering the content at the bottom of the page below the fold. This results in a vertical scrollbar appearing on the body and shifting the content over to the left. This only occurs the browser / os has scrollbars always visible.
Solution Description:
The solution here is to default the popper wrapper with
position: absolute, top: 0, left: 0
so that it begins rendering in the top left corner. Also changed the scroll behavior to be smooth as it helps guide the user to understand where the element came from it if happens to be offscreen.To test all spotlight usage, I had to fix an issue where the guided tour menu item wasn't rendering because of a change to active perspective fetching. This fix required also addressing a circular dependency.
Screen shots / Gifs for design review:
Test Setup
Install the following Quick Start:
Browser conformance: