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

Visualize doesn't render right in IE 11 #66282

Closed
flash1293 opened this issue May 12, 2020 · 3 comments · Fixed by #66555
Closed

Visualize doesn't render right in IE 11 #66282

flash1293 opened this issue May 12, 2020 · 3 comments · Fixed by #66555
Assignees
Labels
blocker bug Fixes for quality problems that affect the customer experience Feature:Vis Editor Visualization editor issues IE11 regression Team:Visualizations Visualization editors, elastic-charts and infrastructure v7.8.0

Comments

@flash1293
Copy link
Contributor

Kibana version: 7.8 BC 1

Original install method (e.g. download page, yum, from source, etc.): cloud

Describe the bug: When going to visualize in IE 11, the container doesn't take up the available height.

Screenshots (if relevant):
Screenshot 2020-05-12 at 20 50 26

@flash1293 flash1293 added bug Fixes for quality problems that affect the customer experience Team:Visualizations Visualization editors, elastic-charts and infrastructure labels May 12, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@flash1293
Copy link
Contributor Author

Also a problem on BC 2

Screenshot 2020-05-14 at 11 25 06

@timroes
Copy link
Contributor

timroes commented May 14, 2020

@cchaos @sulemanof @dziyanadzeraviankina could you have a look into that, please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker bug Fixes for quality problems that affect the customer experience Feature:Vis Editor Visualization editor issues IE11 regression Team:Visualizations Visualization editors, elastic-charts and infrastructure v7.8.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants