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
And to eliminate any chance of the issue being with build modules being out of date on my development machine, I've also used Netlify to automate the deployment of that github repo: https://clever-franklin-bb11e3.netlify.com
The issue does not occur when running a local development server -- only when generating the site for production.
This bug report is available on Nuxt community (#c9682)
The text was updated successfully, but these errors were encountered:
{collapseBooleanAttributes: true,decodeEntities: true,minifyCSS: false,// This is not the defaultminifyJS: true,processConditionalComments: true,removeEmptyAttributes: true,removeRedundantAttributes: true,trimCustomFragments: true,useShortDoctype: true}
UPDATE 2
Interestingly, the underlying repo example works well with font families in singlequotes but not without quotes.
The following code does work on the test page (but still not via yarn generate):
Version
v2.9.1
Reproduction link
https://clever-franklin-bb11e3.netlify.com/
Steps to reproduce
font-family
attribute on the .title element with "Archivo Black"What is expected ?
The font-family for the .title style should be 'Archivo Black'
What is actually happening?
The value is actually reading 'Archivo #000'
Additional comments?
This error was brought up before here:
#5778
But it was closed because the issue couldn't be replicated.
I've provided a github repo with only the above steps replicated:
https://github.com/stevecomrie/nuxtjs-font-replacement-bug
And to eliminate any chance of the issue being with build modules being out of date on my development machine, I've also used Netlify to automate the deployment of that github repo:
https://clever-franklin-bb11e3.netlify.com
The issue does not occur when running a local development server -- only when generating the site for production.
The text was updated successfully, but these errors were encountered: