Breaking: Record and category icons follow the colour scheme
Description
The record icons of this extension were registered with the core provider
\TYPO3\, which renders
the default markup - the markup a
typeicon_ entry reaches - as an
<img>
tag. An image is opaque to CSS, so the icon kept the ink of its
file whatever the backend colour scheme said, and a dark drawing stayed dark on
the dark cards of the record list.
They are now registered with
\FGTCLB\,
which inlines the file in both markups, and the files themselves are drawn in
current with no colour of their own.
That covers the three identifiers of this extension -
academic-,
tx_
and
tx_ - and its four category type
icons, which
EXT: registers as
category_. The four category types ask for it with
inline in Configuration/; without that
flag a category type icon keeps the core provider.
Impact
The four category type icons reach the frontend, through the icon
ViewHelper of academic_base,
<ab:, in
Partials/,
Partials/ and
Partials/, and through
category_ in Partials/.
category_types registers them in the frontend icon registry as
well, with the same provider, see
Important: Category type icons come from the frontend icon registry.
None of those calls asks for the inline markup, so their rendered markup
changes: an
<img>
of a fixed pixel size becomes an inlined
<svg>
with
width="1em" height="1em"
, which follows the font size
and the colour of the text around it. Every site using the partner or
partnership plugins sees those icons resize and recolour.
Site CSS or JavaScript that sized, coloured or addressed the
<img>
has
to address the
<svg>
instead.
In the backend, the academic partner page type icon, the two record icons and
the four category type icons take the text colour around them, so they stay
legible in a dark backend colour scheme.
academic- is also the
icon of the four content elements of this extension, so those follow with it -
the identifier is one icon, not two.
Affected Installations
Every installation of this extension. Installations that render the partner or partnership plugins in the frontend are affected visibly.
Migration
Replace an image selector with an element selector in the site CSS, for example
/* before */
.partner-attributes .icon img { width: 32px; }
/* after */
.partner-attributes .icon svg { width: 1.25em; }
The icon element keeps the surrounding
<span class="t3js- wrapper, so a
selector written against the wrapper needs no change.