Kubeflow UI has a giant div blocking most of the screen space

[cheungringo]

/kind bug

What steps did you take and what happened: I'm a heavy user of the Kubeflow UI to read through logs to debug pipelines that my company runs. For some reason, starting Aug 10th, a giant div (the footer I believe) has appeared and is blocking most of the screen space which makes debugging and visualizing my pipelines very difficult.

What did you expect to happen: Not to have a giant div blocking the screen.

Anything else you would like to add: Please see attached screenshot.

Environment:

• Kubeflow version: (version number can be found at the bottom left corner of the Kubeflow dashboard): build version dev_local
• kfctl version: (use kfctl version): couldn't find this command on kubeflow cluster
• Kubernetes platform: (e.g. minikube): minikube version: v1.26.0
• Kubernetes version: (use kubectl version): Client Version: v1.24.3 Kustomize Version: v4.5.4 Server Version: v1.21.12-gke.2200
• OS (e.g. from /etc/os-release):

[sethjones]

To add a little more information to this report:

• This appeared in one of the latest Firefox releases (for me). I believe it showed up after the FF 103 release.
• Testing in Chromium (104.0.5112.79), and Firefox ESR (91.11.0esr) - I was unable to reproduce.

My setup stats:

• Kubeflow 1.5.0
• K8s 1.21.12

[fabito]

I was able to reproduce the behaviour in Chrome: 104.0.5112.79-1 and 103.0.5060.53-1 It works fine in FF 103.0 (64-bit) though.

[daisuke834]

I also have the same issue with Chrome 104.0.5112.79. It works fine with Safari 15.2 (17612.3.6.1.6) so far.

[ittus]

It seems the issue is caused by browser's LastPass extension. After disabling it, Kubeflow UI works as normal.

https://community.logmein.com/t5/LastPass-Support-Discussions/Lastpass-is-adding-a-CSS-element-below-footer/m-p/291627

[sethjones]

It seems the issue is caused by browser's LastPass extension. After disabling it, Kubeflow UI works as normal.

https://community.logmein.com/t5/LastPass-Support-Discussions/Lastpass-is-adding-a-CSS-element-below-footer/m-p/291627

In testing with my browser where i am experiencing the issue, i was able to confirm that disabling the last pass browser extension removed the issue.

IMO: This issue can be closed as it is related to the Last Pass extension and not Kubeflow.

[google-oss-prow[bot]]

@cheungringo: The label(s) kind/bug cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubeflow/dashboard/issues/62): >/kind bug > >**What steps did you take and what happened:** >I'm a heavy user of the Kubeflow UI to read through logs to debug pipelines that my company runs. For some reason, starting Aug 10th, a giant div (the footer I believe) has appeared and is blocking most of the screen space which makes debugging and visualizing my pipelines very difficult. > > >**What did you expect to happen:** >Not to have a giant div blocking the screen. > >**Anything else you would like to add:** >Please see attached screenshot. > > > > >**Environment:** > >- Kubeflow version: (version number can be found at the bottom left corner of the Kubeflow dashboard): build version dev_local >- kfctl version: (use `kfctl version`): couldn't find this command on kubeflow cluster >- Kubernetes platform: (e.g. `minikube`): minikube version: v1.26.0 >- Kubernetes version: (use `kubectl version`): Client Version: v1.24.3 >Kustomize Version: v4.5.4 >Server Version: v1.21.12-gke.2200 >- OS (e.g. from `/etc/os-release`): > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[nikola-rahman]

+1 with Version 116.0.5845.110 (Official Build) (arm64). Disabling extension Power Thesaurus "solved" the issue for me.

[juliusvonkohout]

/close

[google-oss-prow[bot]]

@juliusvonkohout: Closing this issue.

In response to [this](https://github.com/kubeflow/dashboard/issues/62): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[jaklan]

There are much more extensions causing exactly the same issue - DeepL, Monica, Power Thesaurus etc. KFP is the only webpage I have noticed where they become problematic, so statements like:

IMO: This issue can be closed as it is related to the Last Pass extension and not Kubeflow.

doesn't seem to be correct. Also Chrome doesn't allow to disable single extensions at the specific domain, which makes the issue extremely annoying.

[aehm03]

I had another plugin causing the error. I investigated why it happens on the kubeflow website only and found out that it is most likely due to this line in the styles.css

body>* {
    flex: 1
}

I have limited knowledge of css but I think this will make every child element of body grow to fill the space. Plugins sometimes populate the dom with divs and then decide to keep them empty / hidden but this css setting will make them visible.

@juliusvonkohout, @sethjones could we re-open this?

[juliusvonkohout]

/reopen

[google-oss-prow[bot]]

@juliusvonkohout: Reopened this issue.

In response to [this](https://github.com/kubeflow/dashboard/issues/62): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[aehm03]

Thanks for opening it. I found out that there is already a PR dealing with it: https://github.com/kubeflow/kubeflow/pull/6664

[thesuperzapper]

I am going to move this to the dashboard repo, which we will be migrating the Central Dashboard code to in the near future.

(Currently, the kubeflow/kubeflow repo has no issues, so this one will be missed otherwise).

/transfer dashboard