Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How Fonts Should Degrade Instructions Unclear
See original GitHub issueChallenge Name
Specify How Fonts Should Degrade
Issue Description
Browser Information
- Browser Name, Version:
- Operating System:
- Mobile, Desktop, or Tablet:
Your Code
Screenshot
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Specify How Fonts Should Degrade Basic CSS via ... - YouTube
FOLLOW ALONG LINK: https://www.freecodecamp.org/learn/responsive-web-design/basic-css/specify- how-fonts - should -degradeCheck out the ...
Read more >Specify How Fonts Should Degrade, - HTML-CSS
Anyone know what HTML to add to do this. “In the last challenge, you imported the Lobster font using the link tag. Now...
Read more >Solve problem "Specify How Fonts Should Degrade" online
Solve problem "Specify How Fonts Should Degrade" online - Learn Python 3 - Snakify.
Read more >FreeCodeCamp/Help - Gitter
Your h2 element should degrade to the font Monospace when Lobster is not available. Comment out your call to Google for the Lobster...
Read more >html - Font degradation issue
Here are the directions: Your h2 element should use the font Lobster. Your h2 element should degrade to the font monospace when Lobster...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@erictleung @Manish-Giri Let’s combine them and see what’s best 😊
@Greenheart thanks for pointing that out! I think my suggestion still applies. The confusion stems a little because of the example code and maybe the potentially vague instruction of “your call to Google Fonts”. So specifying that your “call to Google Fonts” was the
<link>tag, I think that will help clear up some confusion.