Currently using a govuk based theme, and it requires support for the exclamation mark within the class names.
Attaching a relevant patch here for reference purposes.
Right now, core uses form_clean_id() in a few places to clean perspective class names before inserting them into the html. But form_clean_id() is the wrong function to clean class names because it enforces a uniqueness to them by appending _0, _1, etc if form_clean_id() has been previously called with the same input.
http://www.w3.org/TR/CSS21/syndata.html#characters shows the syntax for valid class names and IDs.
In CSS, identifiers (including element names, classes, and IDs in selectors):
I'm all for ignoring the 3rd part of that spec (too messy), but we should definitely implement the first 2 parts.
In addition to the validity of classes, we should also look to Drupal’s code style. We currently don't use underscores in class names, so this new function should replace them with dashes by default, but allow callers to relax that restriction if they have a use case (like integrating with 3rd party code.)
Fixed
7.0 ⚰️
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Currently using a govuk based theme, and it requires support for the exclamation mark within the class names.
Attaching a relevant patch here for reference purposes.