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

Fleet: Git Repo: Overview of 'ready' states popup looks and behaves oddly #11967

Open
richard-cox opened this issue Sep 19, 2024 · 0 comments
Open
Labels
area/vue3 kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@richard-cox
Copy link
Member

Setup

  • Rancher version: dev of 2.10.0

Describe the bug
Looks oddly

  • probably just needs a colour matching background rather than white
  • would be good to understand why this specific one is broken and other usages not

Behaves oddly

  • in some situations two clicks are required to open the popover

To Reproduce

  • Continuous Delivery --> Git Repo --> Create --> enter example details --> Create
  • click on new repo to see detail page
  • click on either X / Y Bundles ready or X / Y Resources ready
  • for behaviour issue
    • click between the two popovers, or click outside and open again (couldn't tie down a specific process)

Result
image

Expected Result
Look - Would expect the white colour to be the same as the background colour
Behaviour - After clicking to open the popover it remains open

Additional context
Lookswise, the old popover didn't have an arrow part at all

@richard-cox richard-cox added this to the v2.10.0 milestone Sep 19, 2024
@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 Sep 19, 2024
@rancher rancher deleted a comment Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vue3 kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

1 participant