Needs work
Project:
Drupal core
Version:
main
Component:
entity system
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 Jul 2015 at 04:44 UTC
Updated:
1 Sep 2026 at 17:09 UTC
Jump to comment: Most recent
Problem/Motivation
At the moment we have a mixture of filtering (using the admin tag list) or escaping (SafeMarkup::checkPlain()).
Proposed resolution
We should be consistent and also allow the list of tags that the HTML spec allows in an H1 tag. This permits phrasing elements. Which are (a pretty bizarre list):
a or em or strong or small or mark or abbr or dfn or i or b or s or u or code or var or samp or kbd or sup or sub or q or cite or span or bdo or bdi or br or wbr or ins or del or img or embed or object or iframe or map or area or script or noscript or ruby or video or audio or input or textarea or select or button or label or output or datalist or keygen or progress or command or canvas or time or meter
Comments
Comment #1
alexpottAdding links to HTML5 what goes in an H1 docs.
Comment #2
wim leersThis part makes some sense.
This part makes no sense. WTF!
Fascinating :)
Comment #3
alexpott@Wim Leers - yep it is fascinating. I think we can come up with our own list - it just has to be a subset of the phrasing elements.
Comment #4
alexpottI think this is a major task as predictable behaviour in adding html to titles is very important for usability - and I bet everyone has had an occasion to what to html into a title.
Comment #5
dawehnerJust wanted to point to a related issue: #2350509: Implement auto-route generation for all core entities and convert all of the core entities. ensures that all entity labels are at least rendered the same way.
Comment #6
jibranJust following up on the testing for auto escaping idea. Can we provide a blanket coverage for all entities label just like we have ConfigImportAll test?
+1 #3.
Comment #7
gábor hojtsyDiscussed this as a side issue of #2505989: Controllers render caching at the top level and setting a custom page title lose the title on render cache hits on the critical call. AFAIR agreed that an internal configurable parameter would be fine that a contrib module may provide a UI for if they want to customize it.
Comment #8
wim leersShouldn't we distinguish between
<title>and<h1>?Comment #22
smustgrave commentedThank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #23
smustgrave commentedWanted to bump this 1 more time before closing.
Comment #25
smustgrave commentedBased on the initial discussion this may still be valid. Issue will need some love once it's decided.