-
Notifications
You must be signed in to change notification settings - Fork 185
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
Cant't switch index pattern on PC with resolution lower then full HD #386
Comments
Recheck at my first Notebook Windows 7 x64 SP1 with latest Firefox 74 with display resolution 1366 x 768, situation not change. And one more check was made with Windows 10 x64 with latest Firefox 74 and display resolution 1024 x 768. Same too. |
@jforsec I see you have display issues with smaller resolution. Does index switching work in Firefox 74? I will check once under Windows Firefox 74 locally. |
Hello. Yes, index switсh work in Firefox 74. Problem only with PC where resolution lower then full HD. It's possible to fix? |
I am not sure why index switching is not working ins lower resolution. I can see why the lay button has issue. Let me try if I can test it locally. |
I think switch will work, when all buttons display properly. Thanks, will wait. |
I tested this locally in lower resolution and I see the OK button is not visible. One workaround I suggest is to press |
For me work this one , Select index, TAB, Enter. Will wait normal fix. |
Hello. Any news about fix for this problem? |
Hello. I have a two problem with logtrail or this misconfig.
Elasticsearch, filebeat, kibana 7.5.2
Logtrail 7.5.2-0.1.31
Tested in actual browsers to this time:
Chrome 80.0.3987.132
Firefox 73.0.1
My logtrail.json in ZIP archive.
I use logstash and filebeat. Configure two index for them in logtrail.json after some tuneing i see them both into logtrail. When i try to switch index over settings button this not work. All other work good.
Second problem is less critical. I have problem with Play button. It's show like on screenshot.
The text was updated successfully, but these errors were encountered: