-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Security Solution] Safari browser (13.1.2) crashed on setting per page to 300 under detection rules #84608
Comments
@deepikakeshav-qasource please review |
Reviewed & Assigned to @MadameSheema |
@peluja1012 @spong can you please help to prioritise this? feel free to change the impact if you don't agree with it :) |
@karanbirsingh-qasource please validate this again on the latest snapshot so we can triage. Thank you! |
@karanbirsingh-qasource As of this PR, we only allow users to display up to 100 rules at a time. Do you see similar issues with 100 rules in Safari? |
Hi @peluja1012 thanks for sharing the updated paging change. we have validated this issue on 7.14.0-SNAPSHOT and found it fixed . Now user is able to set row per page to 100 and can view details of all 100 detection rule in mac safari browser. Build Details:
Hence we are closing this issue. c.c @MadameSheema |
Describe the bug
Safari browser crashed on setting per page to 300 under detection rules
Build Details:
Platform: Production
Version:7.10.1 BC1
Commit:
1d4cfde288ede0c4bc6277b4d589ca0cb96b231f
Artifact Page : https://staging.elastic.co/7.10.1-ce3b40e6/summary-7.10.1.html
Browser Details
Safari: 13.1.2(13609.3.5.1.5)
Preconditions
1.Cloud environment having version 7.10.1 BC1 on production should exist
Steps to Reproduce
Note: Issue is occurring on Physical Hardware machine [ High Sierra]
Test data
N/A
Impacted Test case(s)
Actual Result
User not able to set per-page to 300 under detection rule for Safari browser
Expected Result
User should be able to set per-page to 300 under detection rule for Safari browser
What's Working
What's not Working
Screenshots
Logs
N/A
The text was updated successfully, but these errors were encountered: