There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply () below.
If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.
Join the Discussion. Help a fellow learner on their journey.
Ask or answer a question about this exercise by clicking reply () below!
Agree with a comment or answer? Like () to up-vote the contribution!
Each rule refers to one font weight. The lesson says to include normal (400) and bold (700) font weights, so there are two rules. You can see the different font-weight values in each rule.
Fair enough. So then why would posting the exact same code twice make any difference? I’m going out on a limb here to assume that I would need to have one code with the font-weight at 400 and one at 700?
You’re not posting the exact same code twice. The two latin @font-face rule sets look pretty much the same, but if you look at the font-weight and src properties, you’ll see that one is for 400/regular, and the other is for 700/bold.
There may still be some browsers out there that do not support this feature so some fallback may be required to substitute in a font via the <link> element in the HEAD or using a web-safe font we can expect to be on the user’s machine.
Depending on internet connection and download speed, the default font will be drawn in by the browser while it waits for the CSS font to come down. This can be unsettling for some.
Like all new and cutting edge developments, it takes time for universal adoption, sometimes years, so we should consider our audience’s needs before our own desire to be out front with new technologies.
The URL is necessary since that’s where the font is being downloaded from. As for the Unicode range, I would think it would apply on a case by case basis, but cannot give a definitive answer to that. We see above that apart from the first 256 characters (of which only the first 128 are ASCII) the range includes special characters, which if one has the time could be further investigated.
Without further investigation there is no definitive answer to that question. I cannot agree with something about which I am not sure myself. Perhaps there is an answer on CSS Tricks, or elsewhere. I’m sure there must something in the specs to describe this more definitively. Until we have an answer, we should not assume anything.
The purpose of Unicode is to provide a character set that is applicable in any locale. How far your site reaches out to international audiences would be a determining factor as concerns implementing the special characters outside of the typical Latin character set. I’m afraid there is no one pat answer to this question.
[Try running Windows Network Diagnostics](javascript:diagnoseErrors()).
DNS_PROBE_FINISHED_NXDOMAIN
It doesn’t work, even when I use the direct link given from the exercise. I don’t know what’s going on with my browser. The Google Fonts previews don’t even display on my browser either. Using Google Chrome.