- Issue created by @mortona2k
In #3408330 🐛 Routing InvalidParameterExeception Needs review , I patched an error that broke the report page caused by an invalid html tag . I don't know where this came from, but allowing the colon in the tag report route let me see what content has it so I can fix it.
I am thinking it would be better to have a separate report section for invalid html tags and attributes. There is a comment in the routing.yml file about regex for attributes not being broad enough. It would be great to see them all in one place.
Active
1.0
Code