-
Notifications
You must be signed in to change notification settings - Fork 115
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
Separating anchored position and Overlay class #2088
Conversation
🦋 Changeset detectedLatest commit: f566a4f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Uh oh! @jonrohan, the image you shared is missing helpful alt text. Check your pull request body. Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image. Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs. |
Uh oh! @jonrohan, the image you shared is missing helpful alt text. Check your pull request body. Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image. Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs. |
'Overlay--anchorSide-outsideLeft', | ||
'Overlay--anchorSide-outsideRight' | ||
) | ||
this.classList.add(`Overlay--anchorAlign-${anchorAlign}`, `Overlay--anchorSide-${anchorSide}`) |
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.
These will change as getAnchoredPosition falls back to other sides so we might want to thoroughly test this and make sure it isn't regressing.
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 couldn't find these classes in PVC or dotcom codebases. Maybe they were leftover from another iteration? I can pull into a separate PR if we want to test this change more thoroughly
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.
Must be a holdover then. Go ahead and 🔥 🔥 🔥
Authors: Please fill out this form carefully and completely.
Reviewers: By approving this Pull Request you are approving the code change, as well as its deployment and mitigation plans.
Please read this description carefully. If you feel there is anything unclear or missing, please ask for updates.
What are you trying to accomplish?
Dialog overlay wasn't scrolling the body and fixing the header/footer properly. When the revert is applied, it's reverting to
display: block;
instead of thedisplay: flex
that it needs to be. I originally tried to fix this by seeing if there was a better option fordisplay: revert;
but that leads to other problems with the overlay not disappearing.Screenshots
Before
After
Demo
Integration
No
List the issues that this change affects.
Closes https://github.com/github/primer/issues/2375
Risk Assessment
What approach did you choose and why?
Anything you want to highlight for special attention from reviewers?
Accessibility
Merge checklist
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.