This repository has been archived by the owner on Jun 28, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 111
Issue about Dashboard search bar cookie. #55
Comments
Can you try to reproduce this with the latest release 4.5.3 ? |
It does happen with the latest release 4.5.3 . |
@nvrdawn Thank you for verifying this |
I think you are experiencing something similar to elastic/kibana#7801 |
Closed
Thx |
fixed since 4.5.4 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Versions
Kibi: 4.4.2-1
Operating System:
Server: CentOS 6.7
Client: Win10 Pro 1511
Browser:Chrome 52.0.2743.116 m
Behavior
Use search bar and select cookie in the Dashboard.
Expected:
Use selected cookie as filter and refresh this Dashboard.
Actual:
Whole kibi page reloaded, and after reload action the whole page's dark theme did not work properly.
Steps to reproduce the problem
1.Set kibi.yml: kibana.defaultAppId: dashborad/test
Set kibi/Settings/Advanced: dashboard:defaultDarkTheme: true
2.Open kibi page in the browser
3.Type something(such as: "name:") in the search bar and select the cookie(such as: "name: sarufarr")
Then the whole page reloaded, and the dark theme seems crashed.
Forgive my laziness, there is another problem happened when I use kibi recently.
If I click the option button of the visualization window in Dashboard.
(Just the "Pen" beside the delete button "Close" on the left-top of the visualization window.)
The whole Dashboard page will change into white first and jumped into Visualize page.
And then if I click the Dashboard button to jump back to Dashboard page, I notice the visualization window shape changed. It seems that your dashboard layout adaptive algorithm goes wrong. After I refresh the whole page, the layout become correct again.
I'm sorry for my poor English. XD
If you have some doubt about what I wrote, you can E-mail me.
Looking forward to receive your response.
The text was updated successfully, but these errors were encountered: