You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also there is 'font-size: 100%' property on the body which might be incorrectly merged with the rem font-size of the heading. Nonetheless if i remove it the problem persists, so it might be something else. Chrome discards the whole rule if you supply two values for font size.
Result:
If I remove the 100% from the 'font: 400 100% 54px/54px PorscheNextWlaBold' declaration it works as expected and the font is applied. It seems the CSS font shorthand is incorrectly filled.
Expected behavior
Webfont is properly inlined and font declarations are working
Actual behavior (stack traces, console logs etc)
Headlines use Fallback fonts because the font declaration in CSS in wrong.
Library version
2.5.2
Browsers
Chrome 67
The text was updated successfully, but these errors were encountered:
Declaration:
@font-face {
font-family: 'PorscheNextWLa';
src: url('../fonts/PorscheNextWLa-Regular.woff') format('woff');
font-weight: normal;
font-style: normal;
}
Also there is 'font-size: 100%' property on the body which might be incorrectly merged with the rem font-size of the heading. Nonetheless if i remove it the problem persists, so it might be something else. Chrome discards the whole rule if you supply two values for font size.
Result:
![bildschirmfoto 2018-06-06 um 14 08 47](https://user-images.githubusercontent.com/9129687/41037301-2b8dce46-6993-11e8-8457-1d329cc9a225.png)
If I remove the 100% from the 'font: 400 100% 54px/54px PorscheNextWlaBold' declaration it works as expected and the font is applied. It seems the CSS font shorthand is incorrectly filled.
Expected behavior
Webfont is properly inlined and font declarations are working
Actual behavior (stack traces, console logs etc)
Headlines use Fallback fonts because the font declaration in CSS in wrong.
Library version
2.5.2
Browsers
Chrome 67
The text was updated successfully, but these errors were encountered: