Closed (outdated)
Project:
Drupal core
Version:
11.x-dev
Component:
theme system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Sep 2012 at 04:28 UTC
Updated:
14 May 2025 at 15:30 UTC
Jump to comment: Most recent
Comments
Comment #1
bstoppel commentedtagging
Comment #2
podarokhow can we test it?
It would be nice to grab full list of places need for change due to #1290694: Provide consistency for attributes and classes arrays provided by template_preprocess() for possibly upcoming spint
Comment #3
podarokcrosspost
Comment #4
jenlamptonI agree, a list would be helpful so that's what this issue is for.
As we go through template files it will be easy to identify places where we should be using attributes, and are not currently. As we find those places, each one can get an issue, and then we can edit this post and add the link to the other issue, as I have done above under "Attributes issues".
So far I have only found the one, but I'm sure there are others :)
Comment #4.0
jenlamptonadded docs
Comment #5
vlad.dancerHere couple of such things
system.module theme_exposed_filters()
toolbar.module theme_toolbar_toggle()
toolbar.module toolbar_preprocess_html()
toolbar.module toolbar_preprocess_toolbar()
Comment #6
podarok#5 + #4 good to see it indjected into summary
Comment #6.0
podarokremoved other
Comment #7
mitokens commentedComment #8
nod_This issue not having a project is messing with my script
Comment #14
jwilson3The filter-tips.html.twig and accompanying template_preprocess_filter_tips() that ships with Drupal 11 do use Attributes appropriately and provide no default classes anymore.
Since there were no other templates identified that don't follow the recommended use of Attributes, this issue seems irrelevant at this point.