csp_report filter created via logger is marked as invalid

[iam-py-test]

Prerequisites

• I verified that this is not a filter issue
  • Filter issues MUST be reported at filter issue tracker
• This is not a support issue or a question
  • Support issues and questions are handled at /r/uBlockOrigin
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue
  • Your issue may already be reported
• The issue is not present after wholly disabling uBlock Origin ("uBO") in the browser
  • If the issue is still present after wholly disabling uBO in the browser, then the issue is unrelated to uBO
• I tried to reproduce the issue when...
  • uBO is the only extension
  • uBO with default lists/settings
  • using a new, unmodified browser profile (unmodified except the extension my AV autoinstalls & uBo)
• I checked the documentation to understand that the issue I report is not a normal behavior

Description

The logger allows me to create the following filter, but it is marked as invalid when I view it in my filters:

||www.linkedin.com/platform-telemetry/csp?f=g$csp_report,domain=www.linkedin.com

Logger output

A specific URL where the issue occurs

https://br.linkedin.com/in/kembolle

Steps to Reproduce

1. Go to the url
2. Open the logger & reload the page
3. Scroll down until you see a request of type csp_report.
4. Click on it, and click Static filter
5. Click create
6. Go to my filters
7. Note that uBo then marks it as invalid

Expected behavior:

Either the logger does not allow me to create that filter or it is not shown as invalid when viewed in my filters.

Actual behavior:

The logger allows me to create an filter which is marked as invalid when viewed in my filters

Your environment

• uBlock Origin version: uBlock Origin development build v1.35.3rc1
• Browser Name and version: Google Chrome Version 91.0.4472.101
• Operating System and version: I would prefer to keep that private for security reasons