I am wondering why the heck my body fields get this class, after a grep i found it inside the base theme.
Why is this class added in the .theme file (ln. 141)?
It's a pain to remove it in the child .theme file (array_search ...).
If this class is still needed for some reason, shouldn't we add it inside a field--node--body.html.twig? Much easier to override and probably less performance impact?
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | remove-class-text-secondary-teasers-2940608-5.patch | 610 bytes | neslee canil pinto |
| #4 | removed-class-2940608-4.patch | 610 bytes | tanmaykadam |
Comments
Comment #2
hongpong commentedSomewhat related thing i found today: #2941157: custom class does not appear on body field from field_formatter_class. i would concur with you it is better to add on the twig side if anywhere. If this term isn't a special zurb foundation thing i think it should be removed.
Comment #3
serg2 commentedGoing through the v6 foundation css I cannot find "text-secondary" so I think it maybe a left over from v5 or something, either way not required by ZF.
Comment #4
tanmaykadam commentedI have added patch to remove the class "text-secondary" from teasers.
Comment #5
neslee canil pintoRemoved class text-secondary from teaser mode
Comment #6
philosurfer commented#4 and #5 are the same.
I can confirm #4 works.
No longer seeing class applied.
Comment #7
philosurfer commentedComment #9
hongpong commentedThank you everyone for your contributions here!