in here should exist <code></code> element
See original GitHub issueAffected page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-accessibility-by-building-a-quiz/step-17
Your code
`<code>sans-serif</code>
`
Expected behavior
in here should exist element:
<code>sans-serif</code>
Screenshots
System
win11 Firefox
- Device: [e.g. iPhone6, Laptop]
- OS: [e.g. iOS 14, Windows 10, Ubuntu 20.4]
- Browser: [e.g. chrome, safari]
- Version: [e.g. 22]
Additional context
I want to modify it myself,but I don’t know how to deal with it. I don’t know how to find him
Issue Analytics
- State:
- Created a year ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
<a>: The Anchor element - HTML: HyperText Markup Language
The HTML element (or anchor element), with its href attribute, creates a hyperlink to web pages, files, email addresses, locations in the ...
Read more >The 10 Most Common JavaScript Issues Developers Face
If you need help figuring out why your JavaScript isn't working, consult this list of the 10 most common JavaScript issues from a...
Read more >ICD-10-CM Official Guidelines for Coding and Reporting - CMS
“In diseases classified elsewhere” codes are never permitted to be used as first-listed or principal diagnosis codes. They must be used in ...
Read more >Error Messages | Cypress Documentation
Cypress errors because after a command, the subject becomes 'fixed' to a specific element - since it can't retry commands, if the element...
Read more >Checking If An Element Exists in Protractor - Jim Lynch Codes
And here is an example of a BAD assertion statement that won't work right in Protractor tests. it('should have our elements defined', function ......
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 FreeTop 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
Top GitHub Comments
My two cents, for what it’s worth. I think Verdana should remain marked up as code since the instructions are specifically telling the user to use Verdana for the initial font. I’ve found other courses that have the font name marked up as code in the instructions as well. And it just seems that in general, whenever the instructions tell the user exactly what value to add, the value is marked up as code.
And I also think that sans-serif should not be marked up as code since it is referring to a family of fonts and the tests will accept five different fonts for the fallback, so we aren’t telling the user specifically what to use here. I’m guessing any confusion stems from the fact that one of the acceptable fall back fonts is sans-serif itself. Perhaps we could reword this a little?
“…, and use another web-safe font in the sans-serif family as a fallback.”
thank you
—Original— From: "Oliver @.> Date: Fri, Apr 8, 2022 19:10 PM To: @.>; Cc: @.@.>; Subject: Re: [freeCodeCamp/freeCodeCamp] in here should exist <code></code>element (Issue #45629)
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/14-responsive-web-design-22/learn-accessibility-by-building-a-quiz/614206033d366c090ca7dd42.md is the file you need.
We’re in the process of making it easier to search for individual steps, but for now you can search for the title (Step 17 in this case) within that folder. For instance grep -r ‘Step 17’
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>