Change:
```js assert( <del> /s*[^.]h2s*{s*font-family:s*(['"]?)Lobster1s*(;s*}|})/gi.test( </del> <ins> /s*[^.]h2s*{s*font-familys*:s*('|"|)Lobster1s*(,s*('|"|)[a-z -]+3s*)?(;s*}|})/gi.test( </ins> code ) );

Discussion:
Affected page Your code Expected behavior Should pass all test cases 100%, but instead fails on the third test case "You should only use an h2 element selector to change the font". System (please complete the following information): Device: Laptop OS: Windows 8.1 Pro Latest Update Browser: Firefox, Chrome, Opera Version: Latest All Additional context The bug exists at the rule declaration colon where adding a space breaks the test fixtures. The following piece of CSS doesn't pass the tests, despite being valid and correct: While the following passes: Per the W3C Syntax and basic data types documentation, the regex is used to verify CSS rule declarations. I'd like to work on a fix for this if this will be fixed.
The . The regex doesn't allow spaces there. should work
Okay so, there's more than just that. I mentor a student based on the freeCodeCamp curriculum and a few of this bug have turned up so far. What is the Regex flavor? I tried running the Regex you provided in the fix using JavaScript and it fails. Edit: just tried again, worked like a charm.
Should I open another issue that's more general and mention this or continue in this one?
Is there still an issue of concern here
There's a number of other lessons that suffer the same Regex bug, yes.
Hey , I suggest you open a new issue with a list of the affected challenges if you are up to the task.
Sure thing.

<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: This was discussed on the forum and it was suggested I submit it to GitHub. The instructions of this challenge introduce the use of a “generic name” (optional) so I used “monospace” in the generic name. font-family: FAMILYNAME, GENERICNAME; . I would then get the error: " You should only use an h2 selector to change your font", which I was doing. It turns out any use of a generic name won't be accepted. Please update question to say "don't use generic for now" or update possible answer to allow for a generic insert. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version:.. Operating System: Win 10 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): See link above for insight.
. I would support modifying the test to allow for a fallback value as shown in the challenge description. Before opening this up for contribution, though, I'd like some additional feedback to see if there is support for this change.
Thank you, for taking the time to bring this up. Importantly, the instructions do not mention anything about the generic font. In fact, they are quite clear about what is expected. In my opinion, there is no issue here. Also, I do not see this confusion popping up on the forum. Perhaps the point of discussion should be: Is it best-practice to use the generic/fall-back? If so, then we should consider rewriting the instructions, along with the tests. Something to keep in mind: The lesson is about importing a setting the font-family (the next lesson covers this)
I do agree that I haven't seen much confusion for this lesson popping up on the forum. The lesson does ask the camper to set the font-family of the element to - but the next lesson covers the "font degradation" fall-back value. Maybe it would be best to take this note (and the one below it) and move it to the next lesson? !
Yes, I was thinking the same.

It is just, this is the type of information I would expect when first encountering a new property.
I'm not sure I would move it to the next lesson - there's already an example there. What about changing the last three paragraphs to this: If you both want to move it to the next lesson, I'm fine with it - but it seems like generic fonts are described there pretty good.