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

Popper on wrong cluster if list updates #293

Closed
grolu opened this issue Jan 30, 2019 · 1 comment
Closed

Popper on wrong cluster if list updates #293

grolu opened this issue Jan 30, 2019 · 1 comment
Labels
component/dashboard Gardener Dashboard effort/2d Effort for issue is around 2 days exp/intermediate Issue that requires some project experience kind/bug Bug kind/regression Bug that hit us already in the past and that is reappearing/requires a proper solution lifecycle/rotten Nobody worked on this for 12 months (final aging stage)

Comments

@grolu
Copy link
Contributor

grolu commented Jan 30, 2019

When a popper is presented and a new cluster is added to or removed from the list above the cluster for which the popper has been opened, the popper looses its context and now seems to be attached to the wrong cluster.

@grolu grolu added kind/bug Bug exp/intermediate Issue that requires some project experience component/dashboard Gardener Dashboard kind/regression Bug that hit us already in the past and that is reappearing/requires a proper solution size/s Size of pull request is small (see gardener-robot robot/bots/size.py) labels Jan 30, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Apr 1, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 1, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Aug 1, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Oct 1, 2019
@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Dec 1, 2019
@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jan 31, 2020
@ghost ghost added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Apr 1, 2020
@ghost ghost added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 1, 2020
@grolu
Copy link
Contributor Author

grolu commented Jul 29, 2020

I think there is currently nothing we can do about this. I don't think we can influence the behavior. Maybe this issue will be resolved when vue-popper is updated to use popperjs 2 library, see also: RobinCK/vue-popper#133
I will close the issue for now.

@grolu grolu closed this as completed Jul 29, 2020
@gardener-robot gardener-robot added effort/2d Effort for issue is around 2 days and removed size/s Size of pull request is small (see gardener-robot robot/bots/size.py) labels Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/dashboard Gardener Dashboard effort/2d Effort for issue is around 2 days exp/intermediate Issue that requires some project experience kind/bug Bug kind/regression Bug that hit us already in the past and that is reappearing/requires a proper solution lifecycle/rotten Nobody worked on this for 12 months (final aging stage)
Projects
None yet
Development

No branches or pull requests

3 participants