In Drupal 7, thanks to the implementation of l(), an "active" class was automatically added when generating node listing with views, and when the linked entity's URI was the same as the one listed.
With #1979468: ".active" from linkGenerator(), l() and theme_links() forces an upper limit of per-page caching for all content containing links → , this is not the case any more and it's been reported to not be not easily alterable.
Re add the feature as optional, via means of adding a new checkbox form field to control whether or not the active class on links will be enabled. Adding of the actual CSS class is performed via JS.
New Set the active class on links checkbox on views field options. Description: If checked, if the fields link to the current page, an "is-active" class will be added on active links.
New set_active_class boolean on views.row.schema
N/A
Views can now optionally add the "active" css class.
In Drupal 7, thanks to the implementation of l(), an "active" class was automatically added when generating node listing with views, and when the linked entity's URI was the same as the one listed.
With #1979468: ".active" from linkGenerator(), l() and theme_links() forces an upper limit of per-page caching for all content containing links → , this is not the case anymore and it seem's not easily alterable (I can't my way through).
Is there a way to change this behaviour. Are we missing something in core to let us alter that ?
Needs work
11.0 🔥
Last updated
A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The last submitted patch, 151: 2652000-151.patch, failed testing. View results →
Patch #151 worked for me:
Drupal: 10.1.1
PHP: 8.1.14
Views Configuration
HTML
Views Configuration
HTML with config enabled
HTML with config disabled