Problem/Motivation
The twig file https://git.drupalcode.org/project/drupal/-/blob/10.0.x/core/themes/olivero/templates/datetime-wrapper.html.twig need to be refactored as https://www.drupal.org/node/3010558 is fixed.
Proposed resolution
add `font-weight: bold;` for `.form-item__error-message`
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 3333172-2.patch | 1.42 KB | gauravvvv |
Issue fork drupal-3333172
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
gauravvvv commentedI have attached the patch, Please review.
Comment #3
gauravvvv commentedComment #4
gauravvvv commentedComment #5
markconroy commentedHi @Gauravvv
The issue summary says the "twig file needs to be refacored", but this patch only contains CSS changes and removing the todo from the twig file doc block.
Is there any refactoring of the actual twig file needed?
Comment #6
gauravvvv commented@markconroy As https://www.drupal.org/node/3010558 is fixed.
So I have removed the todo comment from the twig file. And added the required CSS on
form-item__error-messageclass. As suggested in parent issue.Comment #7
markconroy commentedThanks @Gauravvv
Adding
boldto the CSS for errors, means that the full error message will be bold. Is that the desired outcome? Or do we want only items with astrongtag in the error message to be bold?Comment #8
gauravvvv commentedYes @markconroy, Same we have done in the parent issue 3010558: Unnecessary element in Umami's form-element template may produce invalid markup.
<strong>may produce invalid markup. To avoid that we're addingboldto the CSS for errors.Comment #9
markconroy commentedYes, but do we want the FULL error message to be in bold? If the error message is:
How can we show bold to only the words "title", "email", and "phone" if we have the full message set to use "bold".
If that's the desired result, then we can mark this RTBC.
Comment #10
smustgrave commentedThink since the .css file has changed that before/after screenshots should be added to the issue summary to show nothing broke.
Comment #11
pradipmodh13 commentedHello @smustgrave,
Can you please share steps to check this error message.
It will easy for me to share screenshot with After and before.
Comment #15
mithun sObserved that all the strong tags in the files are removed, the css of bold for the error message is missing for 11.x. Added the required css and raised a new PR against 11.x branch. Please review.
Comment #16
mithun sComment #17
smustgrave commentedIssue summary is incomplete. See tags
Comment #18
mithun sUpdating the issue summary for the issue.
Comment #20
quietone commentedThe Olivero theme was approved for removal in #3590816: [policy, no patch] Deprecate Olivero and move to contrib.
This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
The deprecation work is in #3595082: [meta] Tasks to deprecate the Olivero theme and the removal work in #3595085: [meta] Tasks to remove the Olivero theme.