CSS Declarations on some fonts have changed, broken displays, and at times do not allow distinguishing between variations.
The css declarations are broken.
Geller headline and Geller text are now changed so they have identical CSS, meaning they can't be distinguished. When I began the project they were geller-headline and geller-text - but those no longer work.
Source Serif 4 is now declared as source-serif-4-extralight, sans-serif; when it's clearly a Serif font. The previous source-serif-4, serif declaration stopped working also.
These both changed halfway through a design & build and broke the display. Now wondering how many other fonts have changed, and how many client sites have switched back to Helvetica and Times.... Could Adobe please address this and let us know what to expect? Thank you.
-
Jen Gfeller
commented
Appreciate the work.
It seems things have been broken for quite a while, because some of my sites are looking much different since this fix.
Hoping this means it's the proper fonts showing everywhere now - will have to make some adjustments.
Thanks again.
-
Hello - this issue has been resolved.
If this is still persisting, please let know. -
Brandon McGivern
commented
This has also happened for two fonts for me in my Web Kits: Bookmania and Univers Next.
- Bookmania is now giving me font-family: "bookmania-black"
- Univers Next Pro Compressed, Univers Next Pro Condensed, AND Univers Next Pro are all giving the exact same: font-family: univers-next-pro, sans-serif;This has broken all of our designs on our web pages. I think this is a bigger issue that needs to be addressed, as things are fully malfunctioning.
from your CSS:
.tk-bookmania-black { font-family: "bookmania-black",sans-serif; }
.tk-univers-next-pro { font-family: "univers-next-pro",sans-serif; }
.tk-univers-next-pro { font-family: "univers-next-pro",sans-serif; } -
Hi Jen - sorry for the trouble here. We are looking into the bug and will update as soon as we know more.