Skip to content
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] Disable authentication provider dialog is overlayed by the footer of the auth provider config page #13377

Open
pmatseykanets opened this issue Feb 11, 2025 · 2 comments · May be fixed by #13410
Assignees
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this regression
Milestone

Comments

@pmatseykanets
Copy link

Setup

  • Rancher version: head
  • Rancher UI Extensions:
  • Browser type & version: Chrome

Describe the bug

To Reproduce

  • Enable an authentication provider e.g. AzureAD
  • Try to disable it
  • Observe the issue with the confirmation dialog

Result

Expected Result

The confirmation dialog should not be overlayed by any other UI elements.

Screenshots

Image

Additional context

@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Feb 11, 2025
@richard-cox
Copy link
Member

the footer needs to stick to the bottom, as well as appear underneath the modal (which makes this issue less likely, but still needs to be fixed)

@richard-cox richard-cox added this to the v2.12.0 milestone Feb 11, 2025
@richard-cox richard-cox marked this as a duplicate of #13405 Feb 13, 2025
@richard-cox
Copy link
Member

#13405 shows that this is a 2.11 regression

@richard-cox richard-cox modified the milestones: v2.12.0, v2.11.0 Feb 13, 2025
@momesgin momesgin linked a pull request Feb 13, 2025 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this regression
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants