STran 1c96981117 Clarify protected status in filter checkboxes ... The UI/UX for acknowledging a filter will be protected/is protected could be clearer. The checkbox implemented currently doesn't make it clear that the acknowledgement is mandatory and filters that are already protected allow for the checkbox to be unchecked even though that doesn't reflect that the filter cannot be unprotected. - Update copy for the protected filter acknowledgement to make it clear that it's a mandatory acknowledgement, not an optional one - Update copy for the error that shows when a filter that should be protected doesn't have the acknowledgement checked - When a filter is already protected, disable the acknowledgement checkbox to indicate this is not mutable Bug: T364485 Change-Id: I667fcca4511dff1ac3ca69930c5b5e5eb5001787		2024-06-06 00:23:39 -07:00
..
parserTests	Merge "Add support for regex string replacements."	2022-05-31 14:54:33 +00:00
parserTestsEquivset	Move parser tests to /unit	2019-08-28 16:36:37 +00:00
phpunit	Clarify protected status in filter checkboxes	2024-06-06 00:23:39 -07:00
selenium	build: Updating npm dependencies	2024-06-04 00:33:18 +00:00