Question:
If the user adds the new tag on the same line as the first tag then the test will fail. The hint will tell the user that they should have two tags, which they do. As soon as the new tag is moved to a new line then the test will pass. If we want to require that new tag be on a separate line then we should mention this in the instructions or give a hint that tells the user it must be on its own line. Otherwise we should update the test to stop checking for this. No response Confirmed in both Firefox and Chrome. No response
Thanks for opening this issue. This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Changes to make: You will need to change this test: The regex needs to become . Explanation: the matches everything but line breaks, so the pattern with matches all the line up to the , in case of two meta tags on the same line, it matches both of them at once. Adding the in front of makes it a lazy matching, meaning it will match as little as possible while satisfying the pattern, and if the two meta tags are on the same line it will end the match at the first . Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.

Your code should have two `meta` elements. ```js <del> assert(code.match(/<meta.*/?>/g).length === 2); </del> <ins> assert(code.match(/<meta.*?/?>/g).length === 2); </ins> ``` Your `meta` element should have a `name` attribute with a value of `viewport`.


Question:
The test should allow that flexbox is only set inside a media query. As the test is written right now it doesn't seem possible. I didn't actually try logging out what the test is accessing. But I would assume from looking at the code that if the selector is inside a media query won't be what is expected. Forum: Allow flexbox to be set inside a media query. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response
Hi I've been looking to this issue and been able to solve it by iterating the rules if it's instanceof CSSMediaRule like the following: I know it's not efficient because media rules can be nested in others and I don't catch this cases, any suggestions how to parse the data in more efficient way? Thanks!
Is this issue still open?
feel free to open a PR if you think you can fix the issue

Your Product Landing Page should use CSS Flexbox at least once. ```js <ins> const hasFlex = (rule) => ["flex", "inline-flex"].includes(rule.style?.display) </ins> const stylesheet = new __helpers.CSSHelp(document).getStyleSheet() const cssRules = new __helpers.CSSHelp(document).styleSheetToCssRulesArray(stylesheet) <del> const usesFlex = cssRules.find(rule => { return rule.style?.display === 'flex' || rule.style?.display === 'inline-flex' </del> <ins> const mediaRules = new __helpers.CSSHelp(document).getCSSRules('media') const usesFlex = cssRules.find(rule => hasFlex(rule)) const usesFlexMedia = mediaRules.find(mediaRule => { return [...mediaRule.cssRules].find(rule => hasFlex(rule)) </ins> }) <del> assert(usesFlex) </del> <ins> assert(usesFlex || usesFlexMedia) </ins> ``` # --seed--


Question:
there is a typo in cramers-rule challenge, is used instead of which is wrong this sentence should be changed to Here is the markdown file Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
Hi, May I work on this issue ?
of course, feel free to open pull request, after you have read the guide line

assert.exists(document.querySelector("div.fb1 > div.fb1a")); ``` <del> You should give the second new `div` a class of `fbab`. </del> <ins> You should give the second new `div` a class of `fb1b`. </ins> ```js assert.exists(document.querySelector("div.fb1 > div.fb1b"));


Question:
I never paid much attention to it before, but after someone tried to add a of 20 seconds to the challenge to pass test 2 (shown below), I think we should modify the wording to make it clear, the user should not purposely make a delay in the call. I was thinking something like the following for a replacement: No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response
Thanks for opening this issue. This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
I am not sure this wording is much better? Do we really need to mention the approximation used in the test? That is, can we make it:
It may not be much better. As far as the approximation being used in the text, it has been that way since the curriculum was ported over from the . I assume it was to account for some users with slow connections or maybe if someone ran the tests closed to midnight? The first commit this test appeared in was created by Quincy over 5 years ago.
To clarify, I am not questioning the need for an assertion approximation. I am questioning the need to mention it in the test text.
I am with you now. Whoever takes this issue on, please change the text to reflect suggestion shown below:

); ``` <del> The /now endpoint should return a time that is +/- 20 secs from now </del> <ins> The `/now` endpoint should return the current time. </ins> ```js (getUserInput) =>


Question:
Two of the typos are minor but one could be confusing In the first paragraph of the instructions (see below), there is a reference to The actual test number to change is and not , so it should be changed to reflect this. n/a No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response_
Hey, I created pull request for this issue.

# --instructions-- <del> Within `tests/2_functional-tests.js`, in the `'Submit the surname "Vespucci" in the HTML form'` test (`// #5`), automate the following: </del> <ins> Within `tests/2_functional-tests.js`, in the `'Submit the surname "Vespucci" in the HTML form'` test (`// #6`), automate the following: </ins> 1.  Fill in the form with the surname `Vespucci` 2.  Press the submit button


Question:
It would make more sense for step 34 to have the filter syntax example, instead of it showing up in the next step. Explain and show the syntax. No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22]
Yes, that totally needs to be done what about step 35? there I think the example is to remind people how to give same rules to multiple selectors. Should that be removed? double blur example?
Not sure if we need a selector list example as long as the hint text shows the selector. But I would like for the hint text to actually specify it as a selector list.

Use the `filter` property to `blur` the painting by `2px` in the `.canvas` element. <ins> Here's an example of a rule that add a 3px `blur`: ```css p { filter: blur(3px); } ``` </ins> # --hints-- You should set the `filter` property to `blur(2px)`.

Create a rule that targets both `.one` and `.two` and increase their `blur` effect by 1 pixel. <del> Here's an example of a rule that increases the `blur` of two elements: ```css h1, p { filter: blur(3px); } ``` </del> # --hints-- <del> You should have a `.one, .two` selector. </del> <ins> You should have a `.one, .two` selector list. </ins> ```js const oneTwo = new __helpers.CSSHelp(document).getStyle('.one, .two');


Question:
in the docs, there is a line that is missing period at the end of it. These should have period in the end of it Here is the markdown file Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
I will work on that

5. Install a code editor of your choice. <del> We highly recommend using [Visual Studio Code](https://code.visualstudio.com/) or Android Studio. We also recommend installing the official [extensions](https://docs.flutter.dev/get-started/editor?tab=vscode) </del> <ins> We highly recommend using [Visual Studio Code](https://code.visualstudio.com/) or Android Studio. We also recommend installing the official [extensions](https://docs.flutter.dev/get-started/editor?tab=vscode). </ins> ## Fork the repository on GitHub


Question:
In the file curriculum/challenges/english/14-responsive-web-design-22/learn-html-forms-by-building-a-registration- There is a typo, "chose" should be "choose". If you would like to fix this issue please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
I would like to work on this
Go for it.
Added updated wording and is linked to issue.
We have two pull requests with the same change.

# --description-- <del> Users will be allowed to chose either a `Personal Account` or `Business Account`. </del> <ins> Users will be allowed to choose either a `Personal Account` or `Business Account`. </ins> To do this, within each of the first two `label` elements, add one `input` element with `type="radio"`.


Question:
The instructions are here: But, using for the practice projects will always result in a meta order error: <details<summaryOutput Testing Penguing Project</summary<pre<codeblock being tested: learn-css-transforms-by-building-a-penguin 1 passing (21ms) 1 failing 1) Check challenges Assert meta order 2022/responsive-web-design Learn CSS Transforms by Building a Penguin must be in order: expected 18 to equal +0 expected - actual -18 +0 </code</pre</details<details<summaryOutput testing Registration Form Practice Project</summary<pre<codeblock being tested: learn-html-forms-by-building-a-registration-form 1 passing (30ms) 1 failing 1) Check challenges Assert meta order 2022/responsive-web-design Learn HTML Forms by Building a Registration Form must be in order: expected 3 to equal +0 expected - actual -3 +0 </code</pre</details
This is the test that keeps failing: Specifically this: Where is consistently

const challengeTitles = new ChallengeTitles(); const validateChallenge = challengeSchemaValidator(); <del> describe('Assert meta order', function () { /** This array can be used to skip a superblock - we'll use this * when we are working on the new project-based curriculum for * a superblock (because keeping those challenges in order is * tricky and needs cleaning up before deploying). */ const superBlocksUnderDevelopment = [ '2022/javascript-algorithms-and-data-structures' ]; const superBlocks = new Set([ ...Object.values(meta) .map(el => el.superBlock) .filter(el => !superBlocksUnderDevelopment.includes(el)) ]); superBlocks.forEach(superBlock => { const filteredMeta = Object.values(meta) .filter(el => el.superBlock === superBlock) .sort((a, b) => a.order - b.order); if (!filteredMeta.length) { return; } it(`${superBlock} should have the same order in every meta`, function () { const firstOrder = getSuperOrder(filteredMeta[0].superBlock, { showNewCurriculum: process.env.SHOW_NEW_CURRICULUM </del> <ins> if (!process.env.npm_config_block) { describe('Assert meta order', function () { /** This array can be used to skip a superblock - we'll use this * when we are working on the new project-based curriculum for * a superblock (because keeping those challenges in order is * tricky and needs cleaning up before deploying). */ const superBlocksUnderDevelopment = [ '2022/javascript-algorithms-and-data-structures' ]; const superBlocks = new Set([ ...Object.values(meta) .map(el => el.superBlock) .filter(el => !superBlocksUnderDevelopment.includes(el)) ]); superBlocks.forEach(superBlock => { const filteredMeta = Object.values(meta) .filter(el => el.superBlock === superBlock) .sort((a, b) => a.order - b.order); if (!filteredMeta.length) { return; } it(`${superBlock} should have the same order in every meta`, function () { const firstOrder = getSuperOrder(filteredMeta[0].superBlock, { showNewCurriculum: process.env.SHOW_NEW_CURRICULUM }); assert.isNumber(firstOrder); assert.isTrue( filteredMeta.every( el => getSuperOrder(el.superBlock, { showNewCurriculum: process.env.SHOW_NEW_CURRICULUM }) === firstOrder ), 'The superOrder properties are mismatched.' ); </ins> }); <del> assert.isNumber(firstOrder); assert.isTrue( filteredMeta.every( el => getSuperOrder(el.superBlock, { showNewCurriculum: process.env.SHOW_NEW_CURRICULUM }) === firstOrder ), 'The superOrder properties are mismatched.' ); }); filteredMeta.forEach((meta, index) => { it(`${meta.superBlock} ${meta.name} must be in order`, function () { assert.equal(meta.order, index); </del> <ins> filteredMeta.forEach((meta, index) => { it(`${meta.superBlock} ${meta.name} must be in order`, function () { assert.equal(meta.order, index); }); </ins> }); }); }); <del> }); </del> <ins> } </ins> describe(`Check challenges (${lang})`, function () { this.timeout(5000);


Question:
When working on the file we are asked to write a function. There is a typo in the last sentence of the info you give. "Make sure the "repsonse" you... no code needed just fix the typo, lol No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response
Thank you for opening this issue. Tutorial is located at: This tutorial is using CodeRoad VS Code extension, specific guidelines how to contribute to them can be found on Making PR for this issue will require following parts referring to making changes on the branch. Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
I can fix this typo :)

return res.redirect('/forgot'); } res.render('account/reset', { <del> title: 'Password Reset' </del> <ins> title: 'Password Reset', token: req.params.token </ins> }); }); };

from: 'Team@freecodecamp.com', subject: 'Reset your Free Code Camp password', text: [ <del> 'You are receiving this email because you (or someone else)', </del> <ins> 'You are receiving this email because you (or someone else)n', </ins> 'requested we reset your Free Code Camp account's password.nn', <del> 'Please click on the following link, or paste this into your', </del> <ins> 'Please click on the following link, or paste this into yourn', </ins> 'browser to complete the process:nn', 'http://', req.headers.host, '/reset/', token, 'nn', <del> 'If you did not request this, please ignore this email and', </del> <ins> 'If you did not request this, please ignore this email andn', </ins> 'your password will remain unchanged.n' <del> ].join(' ') </del> <ins> ].join('') </ins> }; transporter.sendMail(mailOptions, function(err) { if (err) { return done(err); }

extends ../layout block content <del> .col-sm-8.col-sm-offset-2 form(method='POST') legend Reset Password </del> <ins> .col-sm-8.col-sm-offset-2.jumbotron form(action='/reset/#{token}', method='POST') h1 Reset Password </ins> input(type='hidden', name='_csrf', value=_csrf) .form-group label(for='password') New Password


Question:
The language selection menu is not intuitive about the no. of available options. It's a bit paradoxical at the moment: You will not notice additional options until you start scrolling while being on top of the options. You will not start scrolling until you know there are additional options. to '/learn' on 'Menu' down to 'Change Language' the cursor on the options Scrolling while being in the area of the listed options. menu should be very clean and intuitive. "Cancel Change" option should have some form of visual separation. https://user- Device: All Devices OS: All OS Browser: All Browsers Version: All Versions No response
this will start becoming evident with more languages on the list. The quickest and simplest way this can be handled is by slightly increasing the height of the list and decreasing the height of the hover-state highlight (each item). That will leave some space at the bottom of the last item, intuitively letting the user know there is more to be looked at. Currently, the perfect-sized (height) items and the overall height of the list make it difficult to notice more entries. Finally, that "Cancel" option should be a different color or have some form of visual separation.
is this issue still being worked on? If not, I would like to take it.
That makes sense, I thought we fixed that. should be removed for and
or anyone else interested, this is up for grabs.
This is what makes the language menu full length so no vertical scroll bar appears. Originally, I had the language menu set so that a vertical scroll bar would appear if it was taller than the main menu. But it was decided that there shouldn't be a vertical scroll bar, the language menu should be as tall as necessary so no scroll bar was needed. Is this what we still want? Even as we continue to add even more languages?
thanks for bringing this up. Ideally we would need to show as many languages as possible in a viewport and display a minified scroll bar if the list exceeds the height viewport minus of the navigation. We could show a scrollbar initially as you recommended, but the dropdown needs expand further than the main menu if needed.

cursor: pointer; } <ins> #nav-lang-menu li:first-child { border-bottom: 0.1rem solid var(--gray-45) !important; } </ins> button.nav-link:focus { color: var(--tertiary-color); background-color: var(--tertiary-background);

overflow-y: auto; scrollbar-width: auto; /* lang menu should always be full height */ <del> height: 19.9rem; </del> } /* main menu must be at least as tall as lang menu (when displayed)

background-color: var(--gray-10) !important; } <ins> .nav-lang-menu li:first-child .nav-link:hover { color: var(--love-dark) !important; } </ins> .nav-lang-button { display: flex; justify-content: space-between;


Question:
In step 15 of the curriculum called Learn CSS Variables By Building a City Skyline, the instructions fail to provide the name of the variable that is being referenced. The instructions say: Notice that at no point does this paragraph give the exact name of the variable that is to be used to pass this step. ("Add your variable" all of these are not variable names) Instead the instructions should mention the variable name once: To use a variable, put the variable name in parentheses with var in front of them like this: var(--variable-name). Add your variable as the value of the background-color property of the .bb1a class. Whatever value you gave the variable will be applied to whatever property you use it on. In this case, the variable has the value of . So will be used as the value for the background-color property. No response Device: Laptop OS: Windows 11 Browser: Chrome Version: n/a No response
The user is expected to use the variable they created on the last step: That is the only CSS variable that exists at this point in the project. That said, people take breaks between steps, so it can be mildly unreasonable to expect users to remember details from previous steps. Perhaps:
yes please. Also I spent a long time trying to help someone because I didn't realize right away that the variable was being referenced from a previous step. (I could see the hints, but I couldn't understand why the hints were hinting at something I had never seen) (alternate solution that I think would work also is to call out the previous step: "Add the variable you created in the previous step...")
Why not the best of both worlds?
Change the text to: Seems straightforward of a PR. I'll open it for first timers.
Thanks for the update. I had a question about updates and how they make it back to what we see as users in the curriculum. Is there a schedule at all for a release or whenever someone's PR is accepted, it immediately is available to everyone who uses fCC?
Releases aren't done on a specific schedule. We merge into to trigger a staging release (on ), and merge into to trigger a production release.
if no one is working on this issue yet, could i work on this?
Can I work on it if no one works on it?
Anyone can work on an issue - they are not assigned. We merge the first complete PR to address the issue. The desired new text is listed above.
.bb1a { width: 70%; height: 10%; background-color: var(--building-color1); } here i am getting :- The background-color of the .bb1a element should be set. i dont know what to do?????
open a topic on the forum, the repo is not the place to ask for help in solving the steps

# --description-- <del> To use a variable, put the variable name in parentheses with `var` in front of them like this: `var(--variable-name)`. Add your variable as the value of the `background-color` property of the `.bb1a` class. Whatever value you gave the variable will be applied to whatever property you use it on. In this case, your variable has the value of `#999`. So `#999` will be used as the value for the `background-color` property. </del> <ins> To use a variable, put the variable name in parentheses with `var` in front of them like this: `var(--variable-name)`. Whatever value you gave the variable will be applied to whatever property you use it on. Add the variable `--building-color-1` you created in the previous step as the value of the `background-color` property of the `.bb1a` class. </ins> # --hints--


Question:
In step 29 of the Learn HTML Forms by Building a Registration Form challenge, there seems to be incorrect seed code. The checkbox for accepting terms and conditions is missing a , so when the step first opens it displays a plain text input instead of a checkbox. N/A A checkbox should be rendered instead of a text input. ! Device: Laptop OS: Ubuntu 20.04 Browser: Firefox (104), Chrome (105) No response
Whoops! Yeah, that should be fixed. Thanks for opening this issue. This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Sounds good! I'll submit a PR to fix it!

<fieldset> <input id="personal-account" type="radio" name="account-type" /> Personal Account <input id="business-account" type="radio" name="account-type" /> Business Account  <input id="terms-and-conditions" required /> I accept the terms and conditions   <input id="terms-and-conditions" type="checkbox" required /> I accept the terms and conditions  </fieldset> --fcc-editable-region-- <fieldset></fieldset>


Question:
The sentence is worded strangley: We should refphrase this sentence to something like: ! Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response
An issue with the first timers only label is open for contribution by first time contributors only. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the from to
Can i work in this issue ?
Go for it my friend! Just make sure to create a new branch when you make the changes!

# --description-- <del> Add a `title` and a `meta` elements to the `head`. Give your project a title of `Registration Form`, and give a `charset` attribute with a value of `UTF-8` to your `meta` element. </del> <ins> Add a `title` and a `meta` element to the `head`. Give your project a title of `Registration Form`, and give a `charset` attribute with a value of `UTF-8` to your `meta` element. </ins> # --hints--


Question:
This is a common error on this Step - we should modify the hint to point out the capitalization User should receive hint that helps them see the capitalization error No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response
The current hint is: "The new element should have a attribute with the value . You have either omitted the value or have a typo. Remember that attribute values should be surrounded with quotation marks." Technically, the attribute value doesn't need to be wrapped in quotes since there are no spaces in the value. Also, it will pass if you don't use quotes for the value, so this part of the hint seems unneeded and should probably be removed. Are you thinking that we should have a separate test just to check whether the value has been capitalized? Or do you think we just add a warning to the current hint reminding them that capitalization (or lack thereof) matters?
I'm not quite sure what the best way forward would be. I just know what most questions for this step on the forum are related to Loving vs loving.
We do have dynamic hints we can use:

assert($('input[type="checkbox"]')[0]); ``` <del> Your checkbox should still have an `id` attribute with the value `loving`. You may have removed the attribute or changed its value. </del> <ins> Your checkbox should still have an `id` attribute with the value `loving`.  Expected `--fcc-expected--`, but found `--fcc-actual--`. </ins> ```js <del> assert($('input[type="checkbox"]')[0].id === 'loving'); </del> <ins> assert.equal($('input[type="checkbox"]')[0].id, 'loving'); </ins> ``` The text ` Loving` should no longer be located directly to the right of your checkbox. It should be wrapped in a `label` element. Make sure there is a space between the two elements.

assert(labelElem.hasAttribute('for')); ``` <del> The new `label` element should have a `for` attribute with the value `loving`. You have either omitted the value or have a typo. Remember that attribute values should be surrounded with quotation marks. </del> <ins> The new `label` element should have a `for` attribute with the value `loving`.  Expected `--fcc-expected--`, but found `--fcc-actual--`. </ins> ```js const labelElem = $('input[type="checkbox"]')[0].nextElementSibling; <del> assert(labelElem.getAttribute('for').match(/^loving$/)); </del> <ins> assert.equal(labelElem.getAttribute('for'), 'loving'); </ins> ``` The text `Loving` should be nested within the new `label` element. You have either omitted the text or have a typo.


Question:
In the hint below it ask to add variable, but it's similar to how we ask colors to be , which cased confusion to a camper I propose, applying the same approach in ieahleen pull request to skyline variables name, . Although it feels like giving answers outright, variables are case-sensitive and require specific syntax, which I think we should give their steps some lay way in the hints. original issue:
For that you need to use . First argument of is the found value, and can be referenced with . Second argument of is the expected value, and can be referenced with in the hint text. The tests would need to be changed a bit for this to be possible. And I am not even sure how to apprach it, as it's complex values, and there is this annoying thing called spaces.
I thought will trim the spaces, but as showing in the image below it doesn't. That looks like a nightmare, so let's ignore my original suggestion ! the camper mentioned the lack of keyword, what about adding in the hints something like or

assert.include(new __helpers.CSSHelp(document).getStyle('.bb1a')?.background, 'linear-gradient'); ``` <del> You should give the `background` a `linear-gradient` starting from `--building-color1`. </del> <ins> You should give the `background` a `linear-gradient` starting from `var(--building-color1)`. </ins> ```js assert.include(new __helpers.CSSHelp(document).getStyle('.bb1a')?.getPropVal('background', true), 'linear-gradient(var(--building-color1'); ``` <del> You should give the `background` a `linear-gradient` ending at `--window-color1`. </del> <ins> You should give the `background` a `linear-gradient` ending at `var(--window-color1)`. </ins> ```js assert.include(new __helpers.CSSHelp(document).getStyle('.bb1a')?.getPropVal('background', true), 'linear-gradient(var(--building-color1),var(--window-color1))');


Question:
The documentation opens on port 3200 The challenge editor uses ports 3200/3300 There is a clash there. It may need to move one of the two
What do we have to change to fix this issue?
Heya The quickest fix would probably be to change this line: Replacing 3200 with 3400.
And here! So the documentation is updated together
I can make this change if you wouldn't mind!
Thanks for your interest in contributing! You've already contributed to our codebase, however - we prefer to leave issues for folks who are new to our codebase so they have a chance to familiarise themselves.
that's fair! I guess now I know how to do it so it wouldn't make sense for me to contribute.
Reopened because the docs section still need to be updated If you're going to update the docs, update the English file only
is this issue still open
yes the docs tells people to expect port:3200, while we are using port:3400, which may cause confusion. opening a pull request to change the docs will solve this issue for good
do you mind checking it again ,because I think it has already been edited its showing 3400 now
no worries, can you link the change because the documents is talking about port:3200 Here is the docs, that I am talking about
I was talking about the main branch ,the link you sent just now ,it is not main branch
so do I have to make changes in this branch ??
Nope, I was simply confused

"develop": "npm-run-all build:curriculum -p develop:*", "develop:client": "npm run build:curriculum && cd ./client && npm run develop", "develop:server": "npm run predevelop && cd ./api-server && npm run develop", <del> "docs:serve": "docsify serve ./docs -o --port 3200", </del> <ins> "docs:serve": "docsify serve ./docs -o --port 3400", </ins> "e2e": "npm run e2e:dev:run", "e2e:dev:run": "start-test develop ':3000/status/ping|8000' cypress:dev:run", "e2e:dev:watch": "start-test develop ':3000/status/ping|8000' cypress:dev:watch",


Question:
And here! So the documentation is updated together Originally posted by in Following the docs need to be updated
I mean, the documentation should reflect the 3200-3400 change made in .

npm run develop ``` <del> > The documentation site should be available at <http://localhost:3200> </del> <ins> > The documentation site should be available at <http://localhost:3400> </ins>


Question:
Just transcribing issues from crowdin. In this line: There is an extra comma before the anchor element that has to be removed. In this line: There is an incorrect use of parenthesis. It should become This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Hey, I would like to work on this.

# --description--  As a reminder, this project is being built upon the following starter project on ,Replit  or cloned from GitHub.   As a reminder, this project is being built upon the following starter project on Replit  or cloned from GitHub.  `deepEqual()` asserts that two objects are deep equal.

Convert a given date from the Gregorian calendar to the Discordian calendar. <del> Note that in the Discordian calendar (Chaos 1, 3188 YOLD) is (January 1, 2022), in the Gregorian calendar. </del> <ins> Note that the day Chaos 1, 3188 YOLD in the Discordian calendar is the day January 1, 2022 in the Gregorian calendar. </ins> # --hints--


Question:
This markdown table is missing backticks around the variables (third column). This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Hi , this seems like an issue that i can handle. I am new to freecodecamp repository and would love to contribute
Thank you for your interest! I suggest looking at issues that do not have linked PRs already

| Feature | Variable Type | Variable      | Value Type | |:-------:|:------------:|:-------------:|:----------:| <del> | Age | Objective Feature | age | int (days) | | Height | Objective Feature | height | int (cm) | | Weight | Objective Feature | weight | float (kg) | | Gender | Objective Feature | gender | categorical code | | Systolic blood pressure | Examination Feature | ap_hi | int | | Diastolic blood pressure | Examination Feature | ap_lo | int | | Cholesterol | Examination Feature | cholesterol | 1: normal, 2: above normal, 3: well above normal | | Glucose | Examination Feature | gluc | 1: normal, 2: above normal, 3: well above normal | | Smoking | Subjective Feature | smoke | binary | | Alcohol intake | Subjective Feature | alco | binary | | Physical activity | Subjective Feature | active | binary | | Presence or absence of cardiovascular disease | Target Variable | cardio | binary | </del> <ins> | Age | Objective Feature | `age` | int (days) | | Height | Objective Feature | `height` | int (cm) | | Weight | Objective Feature | `weight` | float (kg) | | Gender | Objective Feature | `gender` | categorical code | | Systolic blood pressure | Examination Feature | `ap_hi` | int | | Diastolic blood pressure | Examination Feature | `ap_lo` | int | | Cholesterol | Examination Feature | `cholesterol` | 1: normal, 2: above normal, 3: well above normal | | Glucose | Examination Feature | `gluc` | 1: normal, 2: above normal, 3: well above normal | | Smoking | Subjective Feature | `smoke` | binary | | Alcohol intake | Subjective Feature | `alco` | binary | | Physical activity | Subjective Feature | `active` | binary | | Presence or absence of cardiovascular disease | Target Variable | `cardio` | binary | </ins> ## Tasks


Question:
All the data viz projects were created on our .rocks domain. We just need to replace the codepen URL's with the new addresses in the curriculum files of those five projects. Here's the URL's: https://bar- https://scatterplot- https://heat- https://choropleth- https://treemap- And the
Hey Just to make sure you want this replaced with https://bar- ?
I want to contribute to this project. Please assign me this task.
thank you for your interested in contributing, but this issue is not open for contributions, please look at issues with labels or

# --description--  **Objective:** Build an app that is functionally similar to this: https://codepen.io/freeCodeCamp/full/GrZVaM.   **Objective:** Build an app that is functionally similar to this: https://bar-chart.freecodecamp.rocks.  Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style.

# --description--  **Objective:** Build an app that is functionally similar to this: https://codepen.io/freeCodeCamp/full/EZKqza.   **Objective:** Build an app that is functionally similar to this: https://choropleth-map.freecodecamp.rocks.  Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style.

# --description--  **Objective:** Build an app that is functionally similar to this: https://codepen.io/freeCodeCamp/full/JEXgeY.   **Objective:** Build an app that is functionally similar to this: https://heat-map.freecodecamp.rocks.  Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style.

# --description--  **Objective:** Build an app that is functionally similar to this: https://codepen.io/freeCodeCamp/full/bgpXyK.   **Objective:** Build an app that is functionally similar to this: https://scatterplot-graph.freecodecamp.rocks.  Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style.

# --description--  **Objective:** Build an app that is functionally similar to this: https://codepen.io/freeCodeCamp/full/KaNGNR.   **Objective:** Build an app that is functionally similar to this: https://treemap-diagram.freecodecamp.rocks.  Fulfill the below user stories and get all of the tests to pass. Use whichever libraries or APIs you need. Give it your own personal style.


Question:
There is a typo in Step 45, the word is misspelled. Here is the typo it should be in step 26, is incorrect grammar, it should be or If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
Is anybody working on this issue? if not I would like too
Hello.. I would like to contribute to this issue.. Kindly assign me the same

# --description-- <del> The variables you have assigned have all had values that are numbers. JavaScript has multiple different data types. The next one you will be use is the <dfn>string</dfn>. Strings are used to store things like words or text. Strings are surrounded with double quotes, single quotes, or backticks. Here is an example of declaring a variable with a string: </del> <ins> The variables you have assigned have all had values that are numbers. JavaScript has multiple different data types. The next one you will use is the <dfn>string</dfn>. Strings are used to store things like words or text. Strings are surrounded with double quotes, single quotes, or backticks. Here is an example of declaring a variable with a string: </ins> ```js let developer = "Naomi";

# --hints-- <del> You should use dot notation to access the `innerText` propertry of `text`. </del> <ins> You should use dot notation to access the `innerText` property of `text`. </ins> ```js assert.match(code, /text.innerText/);


Question:
[X] The "CSS" and the have the same value. This is affecting screen reader users since this involves an input and associated label. [ ] The logo in the upper left needs alt text. I would suggest it just be "freeCodeCamp". A lot of them. N/A Resolved Add alt text to the logo. Do we need to add an extra step for this or can we just add it to ? No response Device: [e.g. iPhone 6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04] Browser: [e.g. Chrome, Safari] Version: [e.g. 22] No response
Seeing as the logo is non-functional, do we want the alt to be null? ? If it does require an , then this should get its own step, and a clear description as to why it needs one should be given. I suggest changing the of the (and associated ) to .
Per , the logo does require alt text. Functionality isn't the deciding factor here, it's if the image conveys information (i.e. is not purely decorative), which this image clearly does. Do we want to split this off into its own issue if we are going to create a new step?
I would say yes, but it is not fun to deal with the merge conflict, when two PRs are opened at the same time.
The logo still needs an alt text. The logo is introduced in step 7: That step should be updated to instruct campers to give the an alt text of . The seed code in all subsequent steps should be updated to include that new attribute.
hey may i work on this issue? if so please assign it to me
Hey We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.

Within the `header`, provide context about the page by nesting one `img`, `h1`, and `nav` element. <del> The `img` should point to `https://cdn.freecodecamp.org/platform/universal/fcc_primary.svg`, and have an `id` of `logo`. </del> <ins> The `img` should point to `https://cdn.freecodecamp.org/platform/universal/fcc_primary.svg`, have an `id` of `logo`, and have an `alt` text of `freeCodeCamp`. </ins> The `h1` should contain the text `HTML/CSS Quiz`.

assert.equal(document.querySelector('img')?.id, 'logo'); ``` <ins> You should give the `img` element an `alt` attribute of `freeCodeCamp`. ```js assert.equal(document.querySelector('img')?.alt, 'freeCodeCamp'); ``` </ins> You should give the `h1` element the text `HTML/CSS Quiz`. ```js


Question:
There is a typo in Step 108, the word is single while it should be . Here is the typo in step 102, there is a missing code block in this line it should be this in step 81, there are three missing code blocks in these line they should be If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
I would like to work on this.
feel free to open a pull request, after you have read .
I have opened a PR please let me know if there are any changes or improvements that needs to be done.

assert.equal(weapons[0].power, 5); ``` <del> Your second `weapons` object should have the `name` set to `dagger` and the `power` set to 30`. </del> <ins> Your second `weapons` object should have the `name` set to `dagger` and the `power` set to `30`. </ins> ```js assert.equal(weapons[1].name, 'dagger'); assert.equal(weapons[1].power, 30); ``` <del> Your third `weapons` object should have the `name` set to `claw hammer` and the `power` set to 50. </del> <ins> Your third `weapons` object should have the `name` set to `claw hammer` and the `power` set to `50`. </ins> ```js assert.equal(weapons[2].name, 'claw hammer'); assert.equal(weapons[2].power, 50); ``` <del> Your fourth `weapons` object should have the `name` set to `sword` and the `power` set to 100. </del> <ins> Your fourth `weapons` object should have the `name` set to `sword` and the `power` set to `100`. </ins> ```js assert.equal(weapons[3].name, 'sword');

assert.match(sellWeapon.toString(), /golds*+=s*15/); ``` <del> You should set `goldText.innerText` to gold. </del> <ins> You should set `goldText.innerText` to `gold`. </ins> ```js assert.match(sellWeapon.toString(), /goldText.innerTexts*=s*gold/);

Now you can start the code to fight monsters. To keep your code organized, your `fightDragon` function has been moved for you to be near the other `fight` functions. <del> Below your `weapons` array, define a `monsters` variable and assign it an array. Set that array to have three objects, each with a `name`, `level`, and `health` property. The first object's values should be `slime`, `2`, and `15`, in order. The second should be `fanged beast`, `8`, and `60`. The third should be `dragon`, `20`, and `300`. </del> <ins> Below your `weapons` array, define a `monsters` variable and assign it an array. Set that array to have three objects, each with a `name`, `level`, and `health` properties. The first object's values should be `slime`, `2`, and `15`, in order. The second should be `fanged beast`, `8`, and `60`. The third should be `dragon`, `20`, and `300`. </ins> # --hints--


Question:
I have pass all test case of "Exercise Tracker" challenge except the 7th test case("you can POST to /api/users/:id/exercises with ..."), I tried many way but still can't pass this test case. When i open the console of Chorm, i found the bug "(...).subtingr is not a function" when i click on the button "I've completed this challenge" to submit the `` the console of brower the link into Solution Link on "I've completed this challenge" error This error should be disappear ! Device: [Laptop] OS: [Windows 11] Browser: [Chrome] Version: [106.0.5249.103] No response
~Please provide the link to the project that you submitted~ EDIT: still half asleep sorry, ignore that
Thanks for opening this issue. This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Line contains the typo, should be . Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Hello, I am interested in working on it
hey there, I suggest reading our contributing guidelines! as it says, all issues with and labels are up for grabs
I have fixed this issue and raised a PR.

const res = await fetch(url + '/api/users', { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, <del> body: `username=fcc_test_${Date.now()}`.substingr(0, 29) </del> <ins> body: `username=fcc_test_${Date.now()}`.substring(0, 29) </ins> }); if (res.ok) { const { _id, username } = await res.json();


Question:
There is a typo in Step 174, the structure of the phrase is harming translation effort as mention in crowdin by translator here is the sentence Here is the original issue they have recommended using I recommend something else Removing the code tags, the word if is used as an English word hinting about the keyword, and there is a hint about keyword in the hints, so I don't see an actual use for the code tags.
Your suggestion LGTM
You mean this? That would totally work I think

# --description-- <del> Since you subtracted health from the player, you need to check `if` the player's `health` is less than or equal to `0`. If it is, call the `lose` function. </del> <ins> Since you subtracted health from the player, you need to check if the player's `health` is less than or equal to `0`. If it is, call the `lose` function. </ins> # --hints--


Question:
in the document, the instruction header says this: because how the following instruction looks I agree with the camper suggestion, in the original issue Can we clear the empty line in the code block, it's annoying me here is the file here is the original issue
hiii, Please accept the pull request
Hello Please is this still open? And how can I work on it?

git cherry-pick <commit-hash> ``` <del> 4. Resolve any conflicts, and cleanup, install run tests </del> <ins> 4. Resolve any conflicts, cleanup, install dependencies and run tests </ins> ```console npm run clean


Question:
reported sentence that looks weird, and I agree. it is used in 4 files here is the sentence I noticed in the last file, we are using deepEquel, should we mention that array's variables' respective position matter?
Can I be assigned to this? We can simply improve it as "property with the value of an array".
contribution isn't open for issues with label , you are more than welcome to discuss how to improve it
I would shorten them to just use ... e.g. "Your fifth value should have a array with three strings."
there is no one has provided a better option yet, so I am opening this for contribution, and when the JS is published, we can come back to this when campers are taking the course. You should follow Tom comment here because no one has answered this, I think it doesn't matter If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
Hello Sir, can you assign me this issue? hacktoberfest
how does this sounds? "Your fifth locations value should have a with the value being an array consisting of three strings." I for one think we don't need to over explain this, as the values are described in order most people will put them in that exact order.
Although, we are trying to include everyone, you are right this is me trying to overtune something simple. It's good, but we should keep Tom suggestion. In HTML/CSS projects steps, we are using the same sentence structure that Tom mentioned, so there will be comfort, and subtle hints that is an object that carry variables.
you can open a PR, after reading our guideline. more info in this comment
Your fifth locations value should have a property and an array value with three strings. kept most of the original wordings.
Opened a PR for this issue!

assert.equal(locations[4].name, 'kill monster'); ``` <del> Your fifth `locations` value should have a `button text` property with the value an array with three `Go to town square` strings. </del> <ins> Your fifth `locations` value should have a `button text` array with three `Go to town square` strings. </ins> ```js assert.deepEqual(locations[4]["button text"], ['Go to town square', 'Go to town square', 'Go to town square']); ``` <del> Your fifth `locations` value should have a `button functions` property with the value an array with three `goTown` variables. </del> <ins> Your fifth `locations` value should have a `button functions` array with three `goTown` variables. </ins> ```js assert.deepEqual(locations[4]["button functions"], [goTown, goTown, goTown]);

assert.equal(locations[6].name, 'win'); ``` <del> Your seventh `locations` value should have a `button text` property with the value an array with three `REPLAY?` strings. </del> <ins> Your seventh `locations` value should have a `button text` array with three `REPLAY?` strings. </ins> ```js assert.deepEqual(locations[6]["button text"], ['REPLAY?', 'REPLAY?', 'REPLAY?']); ``` <del> Your seventh `locations` value should have a `button functions` property with the value an array with three `restart` variables. </del> <ins> Your seventh `locations` value should have a `button functions` array with three `restart` variables. </ins> ```js assert.deepEqual(locations[6]["button functions"], [restart, restart, restart]);

assert.equal(locations[7].name, "easter egg"); ``` <del> Your eighth `locations` value should have a `button text` property with the value an array with the strings `2`, `8`, and `Go to town square?`. </del> <ins> Your eighth `locations` value should have a `button text` array with the strings `2`, `8`, and `Go to town square?`. </ins> ```js assert.deepEqual(locations[7]["button text"], ["2", "8", "Go to town square?"]); ``` <del> Your eighth `locations` value should have a `button functions` property with the value an array with the variables `pickTwo`, `pickEight`, and `goTown`. </del> <ins> Your eighth `locations` value should have a `button functions` an array with the variables `pickTwo`, `pickEight`, and `goTown`. </ins> ```js assert.deepEqual(locations[7]["button functions"], [pickTwo, pickEight, goTown]);

assert.equal(locations[5].name, 'lose'); ``` <del> Your sixth `locations` value should have a `button text` property with the value an array with three `REPLAY?` strings. </del> <ins> Your sixth `locations` value should have a `button text` array with three `REPLAY?` strings. </ins> ```js assert.deepEqual(locations[5]["button text"], ['REPLAY?', 'REPLAY?', 'REPLAY?']); ``` <del> Your sixth `locations` value should have a `button functions` property with the value an array with three `restart` variables. </del> <ins> Your sixth `locations` value should have a `button functions` array with three `restart` variables. </ins> ```js assert.deepEqual(locations[5]["button functions"], [restart, restart, restart]);


Question:
There is a typo in Step 156, the word is used to refer to the operator. Here is the typo it should be Can you change the lowercase that refers to the operator in the file, to uppercase , as well? to follow the docs of Mozilla If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first. Happy contributing.
Hello, I would like to work on this issue.
hello,can i resolve the issue?

# --description-- <del> We don't want a player's only weapon to break. The logical or operator checks if two statements are true. </del> <ins> We don't want a player's only weapon to break. The logical AND operator checks if two statements are true. </ins> <del> Use the <dfn>logical and</dfn> operator `&&` to add a second condition to your `if` statement. The player's weapon should only break if `inventory.length` does not equal (`!==`) one. </del> <ins> Use the <dfn>logical AND</dfn> operator `&&` to add a second condition to your `if` statement. The player's weapon should only break if `inventory.length` does not equal (`!==`) one. </ins> Here is an example of an `if` statement with two conditions:

assert.match(attack.toString(), /ifs*(Math.random()s*<=s*.1/); ``` <del> You should use the logical and operator `&&`. </del> <ins> You should use the logical AND operator `&&`. </ins> ```js assert.match(attack.toString(), /ifs*(Math.random()s*<=s*.1s*&&/); ``` <del> You should use the logical and operator to check if `inventory.length` does not equal `1`. </del> <ins> You should use the logical AND operator to check if `inventory.length` does not equal `1`. </ins> ```js assert.match(attack.toString(), /ifs*(Math.random()s*<=s*.1s*&&s*inventory.lengths*!==s*1s*)/);


Question:
in the document, there is a sentence saying this: But this section is talking about assigning proofreading, it should be changed to this: here is the file here is the original issue If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
I can take this up

This will open the user management tools, you will be able to see the list of all the users. <del> Search for the user that will become contributor. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers (<language>)`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. </del> <ins> Search for the user that will become proofreader. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers (<language>)`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. </ins> The user is now a proofreader.


Question:
There's a consistent grammatical issue. The author uses "it's" to indicate possession, when the correct word is "its". Due to this, I am also willing to look for other grammatical errors. They could cause confusion, or, at the very least, annoyance. /Note: this issue is present throughout the entire challenge/ n/a n/a Device: Macbook Air OS: Mac OS Ventura Browser: Chrome This is more of a writing issue than a tech one. I hope that's ok.
Thank you for taking the time to open this. I am only able to see the use of in 2 challenges: step-8 step-10 Would you mind sharing any more?
An issue with the label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the

A useful property of an _SVG_ (scalable vector graphics) is that it contains a `path` attribute which allows the image to be scaled without affecting the resolution of the resultant image. <del> Currently, the `img` is assuming it's default size, which is too large. Correctly, scale the image using it's `id` as a selector, and setting the `width` to `max(100px, 18vw)`. </del> <ins> Currently, the `img` is assuming its default size, which is too large. Correctly, scale the image using it's `id` as a selector, and setting the `width` to `max(100px, 18vw)`. </ins> # --hints--

# --description-- <del> Make the `header` take up the full width of its parent container, set it's `height` to `50px`, and set the `background-color` to `#1b1b32`. Then, set the `display` to use _Flexbox_. </del> <ins> Make the `header` take up the full width of its parent container, set its `height` to `50px`, and set the `background-color` to `#1b1b32`. Then, set the `display` to use _Flexbox_. </ins> # --hints--


Question:
In the document, there is a sentence saying this: But this section is talking about dealing with solutions , it should be changed to this: here is the file If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
Hi there! I'm definitely a first-timer and would like to fix this. You can assign this issue to me.
Hi feel free to open a pull request after you have read our contribution guide
Hey there! I would like to fix this issue,you can assign this to me.
Hey feel free to open a pull request after you have read our contribution guide

If the OP (Original Poster) replies within a freeCodeCamp curriculum help thread with their final solution, blur it and use the **Blurred Spoiler Solution** canned reply. <del> If a user creates a thread asking for feedback on a solution, move the thread to the feedback subforum and blur the solution, as necessary. If the user is only posting the solution to show if off, then unlist the thread and use the **Solutions Thread** canned reply. </del> <ins> If a user creates a thread asking for feedback on a solution, move the thread to the feedback subforum and blur the solution, as necessary. If the user is only posting the solution to show it off, then unlist the thread and use the **Solutions Thread** canned reply. </ins> ### Underage Users


Question:
The instruction starts with: If you look closely, the heart emoji is slightly different. I can see the purple heart has become slightly bigger in Firefox. However, I can't see the difference in Chrome or Edge. We can change the first sentence to: In some browsers, the heart emoji may look slightly larger. (I changed "different" to "larger", so that campers don't have to spend too much time looking for the difference) And the last sentence to: To make it consistent on different browsers, target the div with the heart emoji, and set its font-weight to its original value. https://user- Device: Laptop OS: Windows 10 Browser: Chrome (ver. 107.0.5304.106), Edge(ver. 107.0.1418.35), Firefox (ver. 106.0.5) No response
The difference is not always the size, though. I am unable to reproduce a change in Chrome, but when I was making this, the heart would get a hashed pattern inside. There is a chance Google has changed something. As such, I suggest we keep the use of "different", and go with:
when I was making this, the heart would get a hashed pattern inside. Actually, this information was what I would have wanted as a learner. When I learn coding, I always check what kind of change the code I wrote makes to deepen my understanding. So if my browser doesn't show the difference, I would want to know what kind of difference it is. How about: The heart emoji may look slightly different. The size, color, or nothing changes, depending on your browser.
I think that is too much useless information. We specifically removed information here:
Personally, I don't think so. For example, if you see a forum post saying "The emoji on my page looks different. How can I fix it?" then I guess you would want to ask how different it is. That's what I'm feeling here. However, it seems like losing color was a Chrome's bug: So I think it's okay to forget about colors. I even think it's okay to remove this step if we can allow that slight change in size.
I played with this for a bit and I really don't have a preference here. Most of instructional suggestions sound good to me - removing the step sounds good as well.
I believe both the browser and operating system determine how emotes are rendered.
OK, how about: In some browsers, the heart emoji may look slightly different from the previous step. This way campers can at least know that the "difference" is something caused by what they have done in the previous step, and not that something like they have used wrong emoji (that was my first guess).
Is this up for contribution ?
The "a hashed pattern inside" of heart that mentioned (and I also noticed this a few months ago when translating this step) can be reproduced using the , as shown below. ! We can also think that the STEP 75 imparted knowledge to the learner to control emoji colors (albeit in a different way). Therefore, how about adding the following steps: to add (this may be step 75) font-family: 'Noto Emoji' to the to see the emoji color change (this may be step 76) the lines in the above two steps, then resume the current step 76 procedure (this may be step 77)
I don't see the need to add steps that import and remove a font for this. I'd much rather stick with adding the note "In some browsers, the heart emoji may look slightly different from the previous step." so that we can focus on the concepts this project is actually trying to teach.

# --description-- <del> If you look closely, the _heart_ emoji is slightly different. This is because some of the character's properties were overridden by the `font-weight` style of `bold`. </del> <ins> In some browsers, the _heart_ emoji may look slightly different from the previous step. This is because some of the character's properties were overridden by the `font-weight` style of `bold`. </ins> Fix this, by targeting the `div` with the heart emoji, and setting its `font-weight` to its original value.


Question:
There is an extra quote in the string below it can be removed as it isn't required Here is the file: If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
Can I work on this issue?
Yea, feel free to open PR, after you have read our contribution guideline
I have created the pull request, please review it.
Can i also contribute to this issue?
Yes, there is no pull request that follows the contribution guideline. If you open PR that follows it, that pr will be merged and closes the issue with it
Thank you

}; ``` <del> You can send a <b>DELETE</b> request to `/api/books` to delete all books in the database. The returned response will be the string `'complete delete successful` if successful. </del> <ins> You can send a <b>DELETE</b> request to `/api/books` to delete all books in the database. The returned response will be the string `complete delete successful` if successful. </ins> ```js async (getUserInput) => {


Question: I noticed that the doc describing the process for updating the docs (how-to-work-on-the-docs-) doesn't explicitly say that when adding a brand new doc file, the file should be updated (or evaluated to see if the new file should be listed there). I'm not sure if 100% of new doc files should in fact get to the , but I feel it should be mentioned as a possible area that needs to be looked at when a person is adding a brand new doc file. (ps. About a month ago I created a new doc file for onboarding of mods and the PR was accepted and merged, but no change was made to the because I was unaware of it till just now... I now need to go back to modify this file to 'publish' the new doc) how-to-work-on-the-docs- N/A Update the how-to-work-on-the-docs- to call out the need to evaluate updating the specifically when creating a brand new doc file. No response

To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, they will be made available automatically at the documentation site. <ins> When adding a new file to the `docs` directory, you should evaluate if the file should also be added to the sidebar navigation. We typically create a link in the [`_sidebar.md`](_sidebar.md) file for new and independent guides. Alternatively, You may follow the instructions below on creating an internal link for supporting guides. </ins> ### How to create an internal link If you want to create a link targeting a different section of the contributing guidelines, follow this format:

- We serve this file as a SPA using `docsify` and GitHub Pages. - The `docsify` script generates the content of `markdown` files in the `docs` directory on demand. - The homepage is generated from the [`_coverpage.md`](_coverpage.md). <del> - the sidebar navigation is generated from [`_sidebar.md`](_sidebar.md). </del> <ins> - The sidebar navigation is generated from [`_sidebar.md`](_sidebar.md). </ins> ### Serving the documentation site locally


Question:
In : Step 43 Increase the psuedo-element's transparency by 30%. psuedo instead of pseudo just loading the page change for : Increase the pseudo-element's transparency by 30%. !
Thanks for opening this issue. This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Hey We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.
currently following the guideline to make my PR

# --description-- <del> Increase the psuedo-element's transparency by `30%`. </del> <ins> Increase the pseudo-element's transparency by `30%`. </ins> # --hints--


Question: In step , currently, the instruction says: The at the beginning of the other commands at the bottom stands for "meta". It's a key that doesn't exist on most keyboards. If you're on OSX it means press then then the letter. If you are on another system, press then the letter. Use the exit command to get back to the terminal. Instead of this, the instruction should be as follows: The at the beginning of the other commands at the bottom stands for "meta". It's a key that doesn't exist on most keyboards. If you're on OSX it means press then the letter. If you are on another system, press then the letter. Use the exit command to get back to the terminal. NOTE: There's an extra then in the third sentence i.e. If you're on OSX it means press then the letter. In step , currently, the instruction says: That construction team must be working hard Open the file again to continue building. Instead of this, the instruction should be as follows: That construction team must be working hard . Open the file again to continue building. NOTE: There's a missing full stop ( ) after within the first sentence. In step , the instruction should be as follows: The at the beginning of the other commands at the bottom stands for "meta". It's a key that doesn't exist on most keyboards. If you're on OSX it means press then the letter. If you are on another system, press then the letter. Use the exit command to get back to the terminal. In step , the instruction should be as follows: That construction team must be working hard . Open the file again to continue building. <img width="707" alt="image" src="https://user-"<img width="706" alt="image" src="https://user-"- Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110

h4.negative-10.text-nowrap Community Builder img.profile-image(src='https://s3.amazonaws.com/freecodecamp/branden-byers.jpg' alt="Branden Byers picture") h4.text-nowrap Madison, Wisconsin <del> p.negative-10 "I'm a massage therapist and Stay-at-home-dad. I learned Hypercard, then Rails, but now I feel at home with JavaScript." </del> <ins> p.negative-10 "Cookbook author and stay-at-home-dad. Started coding as a kid, got distracted, but now I'm back in full JavaScript force!" </ins> .col-xs-12.col-sm-4.col-md-3.team-member h3.negative-10.text-nowrap Michael Johnson h4.negative-10.text-nowrap Nonprofit Coordinator

h4.negative-10.text-nowrap Live Content Manager img.profile-image(src='https://s3.amazonaws.com/freecodecamp/jason-rueckert.jpg' alt="Jason Rueckert's picture") h4.text-nowrap Seattle, Washington <del> p.negative-10 "My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid." </del>  No newline at end of file <ins> p.negative-10 "My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid." </ins>


Question:
Been puzzling over why so many people see the instructions in step 4 of the cat photo app and ignore the requested location of "above the p element" when adding their new comment line of code. Discussed with and he noticed that the editor doesn't show an empty line where it expects the code to go (usually it does on other steps). This issue then is to request a blank line be to the editor for step 4 above the p element line to show where the expected new line of code should be written. Editor should display a single blank line above the p element. No response not applicable Example of forum post where learner just doesn't understand how the code can be -above- discussion in the contributors area of the discord channel (start point here )
I don't have an option for this. However, I do think that we should take away the empty space that is created below the tag as there is no reason why it needs to be there, and might lead to confusion.
Hi and I want to work on this issue. Could you assign it to me?
Issues don't get assigned so just create a new branch and get to work! Make sure you have read the rules for contributing:
Whoops, I have missed a step If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.

CatPhotoApp

Cat Photos
 --fcc-editable-region--
Click here to view more cat photos.
 --fcc-editable-region--


Question:
Describe the bug there are situations in which you need to add special character (like ) which is fine, but for RTL the direction is reverted so the placement of the special character is reverted, as well. Here is the file Likely we have the CSS property to fix this, we simply need the element to wrap that word so we can apply them. To fix this issue wrap the , between markdown code, like this , so the sentence will be something like this If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
There is a second mentioning of .exe in this sentence if it changed to too, that would be awesome
Hi, Has this issue been assigned to someone? If not, could you please assign this to me?
We don't assign issues, feel free to open PR after reading our docs

<details><summary>Installing MailHog on Windows</summary> <del> Download the latest version of MailHog from [MailHog's official repository](https://github.com/mailhog/MailHog/releases). Locate and click on the link for your Windows version (32 or 64 bit) and a .exe file will be downloaded to your computer. </del> <ins> Download the latest version of MailHog from [MailHog's official repository](https://github.com/mailhog/MailHog/releases). Locate and click on the link for your Windows version (32 or 64 bit) and a `.exe` file will be downloaded to your computer. </ins> When the download completes, click to open the file. A Windows firewall notification may appear, requesting access permission for MailHog. A standard Windows command line prompt will open where MailHog will be running once firewall access is granted. <del> Close MailHog by closing the command prompt window. To start MailHog again, click on the MailHog executable (.exe) file that was downloaded initially - it is not necessary to download a new MailHog installation file. </del> <ins> Close MailHog by closing the command prompt window. To start MailHog again, click on the MailHog executable (`.exe`) file that was downloaded initially - it is not necessary to download a new MailHog installation file. </ins> Start [using MailHog](#using-mailhog).


Question: The catphotoapp project’s step 16 asks users to use a section element however if a user type Section as the tag name, the test rejects the code even though html tags are supposed to be case insensitive. It is expected that this code passes since the correct section element is being created. No response Not applicable Issue found on the forum

Your `section` element should have a closing tag. Closing tags have a `/` just after the `<` character. ```js <del> assert(code.match(/</section>/)); </del> <ins> assert(code.match(/</sections*>/i)); </ins> ``` The entire `section` element should be between the opening and closing tags of the `main` element.

  --fcc-editable-region--
CatPhotoApp

Cat Photos

Click here to view more cat photos.
   --fcc-editable-region--


Question:
Describe the bug A clear and concise description of what the bug is. In this string, we are missing code tags around the word . We can change it to this string Here is the file If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
Hey, I can do it
Hey ! Could you please assign it to me. I would be glad to start contributing in open-source with freeCodeCamp.
There is no assignment, you can open a PR, after you have read out our guidelines

# --description-- <del> JavaScript is a powerful language which allows you to build websites that are interactive. To get started, create your standard HTML boilerplate with a `DOCTYPE`, `html`, `head`, and `body`. Include a `title` element and a `link` for your stylesheet, and your `meta` tag for the `charset`. Then, create a `div` element with the id `game` within your `body`. Use the text `RPG - Dragon Repeller` for your `title` element. </del> <ins> JavaScript is a powerful language which allows you to build websites that are interactive. To get started, create your standard HTML boilerplate with a `DOCTYPE`, `html`, `head`, and `body`. Include a `title` element and a `link` for your stylesheet, and your `meta` tag for the `charset`. Then, create a `div` element with `id` set to `game` within your `body`. Use the text `RPG - Dragon Repeller` for your `title` element. </ins> # --hints--


Question:
Creating a new issue specifically to track discussion for the tag system - spinning off of . This also follows up on
Here's some notes I wrote down from our meeting: Make a "tags" dropdown or something expandable in the block descriptions. When expanded, it would list all the tags that are used in steps within that block. When you click on a tag, it filters the steps in the grid display to only show steps with that tag.
Just throwing out some more requirements/suggestions/questions on what we would need to do to enhance accessibility. The user would need to know what tag the grid is currently filtered on (or if not filtered at all), even if the tags dropdown is contracted. It might be helpful to include a "clear filter" button so that keyboard users don't have to navigate through the tags in order to undo a filter. This button could be displayed only when the list is filtered. The previous/next step keyboard shortcuts will come in handy here to allow users to quickly go through the filtered steps until they find what they are looking for. I've heard remarks in the past that these particular shortcuts are intended for power users and thus discoverability isn't a big concern. But with this functionality I think they are now intended for everyone and we should make sure that everyone knows they are available. If we are going to list all of the possible tags in the dropdown then the tags themselves would need to be implemented with an element that can communicate its state (i.e. whether it is the current filter). A would work using the attribute (this is probably my preferred suggestion at this point). A checkbox would work, although a group of checkboxes usually allows for multiple checkboxes to be selected, so we might be going against expected behavior in this case. Another option would be to use a for the tags. Then we wouldn't need a separate dropdown for this (or a clear button), but we would most likely need to add a button since we wouldn't want the filter to apply when the user is merely scrolling through list to view the filters.
For this design, the goal was to create tags with topics that will show up under the "Start Project" button. When clicked, they will highlight the blocks of steps that are connected to the tag’s subject. While designing, I had the following considerations in mind: People with visual impairments should be able to use this feature like everyone else, therefore we shouldn’t rely solely on color or contrast to differentiate the relevant numbersOne posible option could be to have a small text somewhere explaining what the tags do for those who are not familiar enough with technology and don’t understand that these are linksIf there could potentially be like 50 tags, we need to come up with a way to make them look easy on the eye so the users will want to interact with them and not be intimidated or confused, otherwise if they look cluttered users will ignore them due to how difficult they are to read. This is why I made the tags a bit bigger, especially because the tag section can be hidden as you'll see in the design The final draft I made today can be found on the lower right side of the figma file, the frame where the flow starts is called "Second iteration". If you choose this frame you can interact with the prototype, here's a screenshot for reference: <img width="1008" alt="Screen Shot 2022-12-19 at 5 00 18 PM" src="https://user-"?node-id=239%3A953&t=6BabYSgem7caPwLG-1)where you can explore the process, some of my notes and the final design And this is a quick video showing you where to find the prototype and the flow itself. For some reason the video saved at half speed so it is extra slow Bu the way, this is just an initial draft that needs refining once we can discuss it. The design of the "See all steps" button particularly needs more work and I've just put it there as a placeholer, we may in fact replace it with a "clear filters" button and also change it's location. https://user-
I like what you've done here and you incorporated my first two bullet points above! I just have a few suggestions at this time: It would be best if the name for the toggle button that opens/closes the list of tags stays the same for both states. Perhaps just keep it as "Filter steps by topic"? We will use the attribute on the button itself to let screen reader users know which state it is in. The issue with changing the name on toggle is that some screen readers might not immediately pick up the change. Also, using the attribute is an accessibility best practice and it wouldn't make logical sense to change the name when using that attribute. I would vote for "Clear filter" as it would be more consistent with using "filter" on the toggle button. If we change the name on the toggle button to something that doesn't use "filter" then whatever that is, I think the clear button should use that same name for consistency's sake.
Great! If you guys like the design I can start converting it to a final draft, which includes the accessibility comments above
?page-id=234%3A62&node-id=239%3A953&viewport=-694%2C-189%2C0.53&scaling=min-zoom&starting-point-node-id=235%3A242) <img width="691" alt="Screen Shot 2022-12-28 at 1 28 02 PM" src="https://user-"
Thanks for sharing those designs, The idea is really taking shape and the mockups look great. The only thing that leapt out to me was that there's quite a bit of empty space in the filtered view. What do you think to collapsing the gaps between the filtered steps? e.g. rather than having it would just be . That way, even for projects with lots of steps, there's no risk that people fail to notice that later steps are unfiltered, even if they would otherwise be off the page.
I think that's a good idea, here's a quick mockup showing what the design would look like with that modification <img width="369" alt="Screen Shot 2023-01-04 at 12 19 55 PM" src="https://user-"
Thanks I think that looks great.
Great job on the mocks Here is a minimal version if we decided to go down that route: <img width="528" alt="Screen Shot 2023-01-06 at 8 35 27 PM" src="https://user-"
I'm really happy to see this idea taking shape :) Regarding the two designs, I don't have a strong preference between the two, perhaps can weigh in on accessibility. I like the design of the tags of but I think is a little easier to implement and takes up less space
Just to clarify, are we allowing multiple tag filters at at time, or just one?
I'd start with one. If that feels too limiting we can consider allowing more, but I suspect it'll be fine in practice.
Assuming we only allow one tag at a time, in the minimal design, is that supposed to function as a traditional element? Or is it similar to the original design in which it acts as a disclosure button?
Could you clarify?
Hello Following up on your discussion, I would like to take this one!
I think we decided that we want to use something similar Ahmad's mock to start. The argument for keeping the full grid is that campers can see where they are and also where the challenge is that has that tag. As far as the dropdown, we can start with that but may want to show the tags. We are going to add a help wanted label on this and can fine tune some things on the PR. Feel free to work on it if you want or anyone else
If we allow multiple tags at a time, are those going to be OR'd together or AND'd together?
I think we'd want OR (i.e. the union). Reason being there should not be many lessons with multiple tags, so AND would typically be empty.
Ya, that was my thought too. here's another update for your PR :slightlysmilingface:
I would like to work on this issue
We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.
We have decided not to implement this feature.

{ <del> "node": true </del> <ins> /* * ENVIRONMENTS * ================= */ // Define globals exposed by Node.js. "node": true, /* * ENFORCING OPTIONS * ================= */ // Force all variable names to use either camelCase style or UPPER_CASE // with underscores. "camelcase": true, // Prohibit use of == and != in favor of === and !==. "eqeqeq": true, // Suppress warnings about == null comparisons. "eqnull": true, // Enforce tab width of 2 spaces. "indent": 2, // Prohibit use of a variable before it is defined. "latedef": true, // Require capitalized names for constructor functions. "newcap": true, // Enforce use of single quotation marks for strings. "quotmark": "single", // Prohibit trailing whitespace. "trailing": true, // Prohibit use of explicitly undeclared variables. "undef": true, // Warn when variables are defined but never used. "unused": true, // Enforce line length to 80 characters "maxlen": 80 </ins> }

<ins> { /* * ENVIRONMENTS * ================= */ // Define globals exposed by modern browsers. "browser": true, // Define globals exposed by jQuery. "jquery": true, /* * ENFORCING OPTIONS * ================= */ // Force all variable names to use either camelCase style or UPPER_CASE // with underscores. "camelcase": true, // Prohibit use of == and != in favor of === and !==. "eqeqeq": true, // Suppress warnings about == null comparisons. "eqnull": true, // Enforce tab width of 2 spaces. "indent": 2, // Prohibit use of a variable before it is defined. "latedef": true, // Require capitalized names for constructor functions. "newcap": true, // Enforce use of single quotation marks for strings. "quotmark": "single", // Prohibit trailing whitespace. "trailing": true, // Prohibit use of explicitly undeclared variables. "undef": true, // Warn when variables are defined but never used. "unused": true, // Enforce line length to 80 characters "maxlen": 80, // Enforce placing 'use strict' at the top function scope "strict": true' } </ins>


Question:
In the certification project pages, the tab on the left is "Instructions". However, if you resize the browser and the page switches to the mobile layout, the tab name changes to "Info". The "Console" on the desktop layout changes to "Tests" too. and other certification projects with built in editor to the browser Use the same name for the same content. ! ! Device: Laptop OS: Windows 10 Browser: Chrome Version: 108.0.5359.125 No response_
Technically, I don't think this is a WCAG failure. does address consistent identification of functional components. In this scenario, in wide view they are HTML buttons but in narrow view they are tabs, so technically they are not the same component and thus don't fall under 3.2.4. But for usability I would tend to agree that it would be best if they could use the same terminology since they basically do the same thing.
We can use "Console" for both mobile and desktop. Do we use "info" for the desktop layout and call it ?
I agree with using "Console" for both. For the panel showing user stories I would prefer using "Instructions" since the word "Info" seems too vague.
To solve this issue: use "Console" and "Instructions" for both layout. If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
We might want to keep in mind that is much longer than . We do not have much real-estate on mobile.
Here are words that I can think of are "details", "step", "story", "task", "manual", "guide", and "briefing". Is any of them good enough, or do we change the console for now and come back for "instructions" later?
My initial thought is: keep everything consistent, and just use the current mobile-naming for desktop as well. However, I am not entirely happy with the word for what it denotes. might be one option, but I also like your suggestion of .
I find or interesting . I vote for too, if no one else has issue with it, we can go with it, otherwise we go with .
I think is a term in agile development so I'm not sure if we can call it just . I would vote for or if is too long. However, my main concern was that the word changes as the user resizes the window. So, I'm okay with either of them as long as we use the same word for both layouts.
We decided to go with the desktop terms for both, "Instructions" and "Console". The file that needs to be changed is We are going to make another issue about improving the mobile UX to potentially use icons or another solution.
I think that should remain for responsive design issues on cell phones and since it is the appropriate term when the student goes to vsCode or another IDE

{!hasEditableBoundaries && ( <TabPane eventKey={Tab.Instructions} <del> title={i18next.t('learn.editor-tabs.info')} </del> <ins> title={i18next.t('learn.editor-tabs.instructions')} </ins> tabIndex={0} > {instructions}

</TabPane> <TabPane eventKey={Tab.Console} <del> title={i18next.t('learn.editor-tabs.tests')} </del> <ins> title={i18next.t('learn.editor-tabs.console')} </ins> {...editorTabPaneProps} > {testOutput}


Question:
In crowdin, I noticed that step 48 of the new JS course, build an rpg, uses a sentence that may need a grammar correction. Instead of “your button innerText” it should say “your buttons’ innerText”? Full sentence was: Grammar correction. No response N/A No response
Hello , Can you assign me this?
Should be changed to:
Thanks for opening this issue. This looks like something that can be fixed by "first-time" code contributors to this repository. Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.

# --description-- <del> In your `goTown` function, update your button `innerText` properties to be `Go to store`, `Go to cave`, and `Fight dragon`. Update your `onclick` properties to be `goStore`, `goCave`, and `fightDragon`, respectively. Finally, update your text's `innerText` property to be `You are in the town square. You see a sign that says Store.`. </del> <ins> In your `goTown` function, update your `button` elements' `innerText` properties to be `Go to store`, `Go to cave`, and `Fight dragon`. Update your `onclick` properties to be `goStore`, `goCave`, and `fightDragon`, respectively. Finally, update your text's `innerText` property to be `You are in the town square. You see a sign that says Store.`. </ins> # --hints--


Question:
The updated topic banner on the is covering up a couple of the table headers here <img width="1087" alt="Screen Shot 2023-01-03 at 9 51 13 PM" src="https://user-" to for a new update topic banner to show up on homepage. the issue There should be some space between the banner and the table headers in the forum like it was before. <img width="1112" alt="Screen Shot 2023-01-03 at 9 47 33 PM" src="https://user-"- Device: [mac book pro] OS: [MacOS] Browser: [ Chrome] No response
div id="ember47" class="categories-and-latest ember-view" Try adding a padding-top to this element. I used around 100px
this issue may be with the discourse forum, itself. If it's in the discourse forum and it's repeated in different forums, not just freeCodeCamp, then it should be solved there. Removing the below properties fixed it in my devtools.
I looked at the following communities that use discourse and didn't notice the problem there. At first glance, it looks like it is only on the fcc forum page.

| passport-linkedin-oauth2        | Sign-in with LinkedIn plugin.                                        | | passport-oauth                  | Allows you to set up your own OAuth 1.0a and OAuth 2.0 strategies.   | | request                         | Simplified HTTP request library.                                     | <del> | lodash                          | Handy JavaScript utlities library.                                   | </del> <ins> | lodash                          | Handy JavaScript utilities library.                                   | </ins> | uglify-js                       | Dependency for connect-assets library to minify JS.                  | | mocha                           | Test framework.                                                      | | chai                            | BDD/TDD assertion library.                                           |


Question:
Describe the bug Having special character in the slug, title, or heading of the challenges lead to broken structure as shown in the image below. Originally reported by ! These challenges are the translation of these. ! Although we can not add them in the Arabic translation, this is a fix to the side effect, because Arabic isn't the only RTL language with translation efforts. I think it's better to not include special characters in the heading, if they aren't wrapped in spaced, example 'the Logical And Operator &&'. So I suggest two solutions: Delete special character, if they aren't wrapped around spaces, like change "push()" to "push". Add code block around functions and methods, to be something like .
Would it be acceptable to spell these out a little more? Instead of We could do Not only do we get rid of the special characters but it possibly makes it a little clearer for people listening to the page.
In translation, that's perfectly fine . Good call.

--- id: 56bbb991ad1ed5201cd392cc <del> title: Manipulate Arrays With pop() </del> <ins> title: Manipulate Arrays With pop Method </ins> challengeType: 1 videoUrl: 'https://scrimba.com/c/cRbVZAB' forumTopicId: 18236

--- id: 56bbb991ad1ed5201cd392cb <del> title: Manipulate Arrays With push() </del> <ins> title: Manipulate Arrays With push Method </ins> challengeType: 1 videoUrl: 'https://scrimba.com/c/cnqmVtJ' forumTopicId: 18237

--- id: 56bbb991ad1ed5201cd392cd <del> title: Manipulate Arrays With shift() </del> <ins> title: Manipulate Arrays With shift Method </ins> challengeType: 1 videoUrl: 'https://scrimba.com/c/cRbVETW' forumTopicId: 18238

--- id: 56bbb991ad1ed5201cd392ce <del> title: Manipulate Arrays With unshift() </del> <ins> title: Manipulate Arrays With unshift Method </ins> challengeType: 1 videoUrl: 'https://scrimba.com/c/ckNDESv' forumTopicId: 18239


Question:
The instructions state "In your fourth tr element, add a th element with the text Total Liabilities." However it is not really clear that the user should or should not include a period. Users will have failed previous tasks if the period was omitted (periods are required on previous exercises) , therefore they will most likely add the period which will result in a failed test case. Also, if the period is included after "Liabilities", the error message gives "Your th element should have the text Total Liabilities." Which does not highlight the actual issue. Maybe making a different test case message that looks for the period would make it more understandable? The code above should highlight the issue of the period being present. The test case that is currently in place can confuse users that they have a spelling issue/spacing instead of the actual issue being the period at the end of "Liabilities". No response Device: Desktop OS: Windows 10 Browser: Chrome Version: Version 108.0.5359.125 No response
I was thinking, that we could change to But this doesn't make a coherent sentence. I am in favor of adding a new test.
I also think a new test case would be good.
Hi! We just opened a to fix it, but it was not accepted . Could you please kindly inform us some feedback about what was going wrong and what else we need to do? So that we can know where to focus. We appreciate any help, thank you!!
Hi Thanks for reaching out and creating a pull request. For reasons of sanity, we can't accept PRs from forks that organizations maintain. You should make a PR from your own personal GitHub account. You can collaborate with others and have commits made by multiple people, but one person needs to create the PR, and then others may push to the same PR should they wish. It is OK if you want to use the draft mode while collaborating. The person making the PR is responsible for ensuring the checklist is followed, tests are working, and so on. You can also commit on someone's behalf. See: Also, please create good, small, and succinct commit messages and PR titles. Keep your commits clean and avoid any merge commits unless you have conflicts to resolve. The final PR should not have dirty commits from collaborating on an organization fork like the previous PR. The reason is the maintainers of this project will need to validate your changes and the source of the commits. Keeping it clean makes everyone's lives easy. Thanks and happy coding!
Hi Mrugesh! Thank you for your precious feedback! I've switched back to my personal GitHub account, and made a pull request . This time the commits are clean and the messages are concise. Thank you for taking time reviewing! I appreciate any feedback. :D

assert(document.querySelectorAll('table')?.[1]?.querySelector('tbody')?.querySelectorAll('tr')?.[3]?.querySelector('th')); ``` <ins> Your text `Total Liabilities` should not include period `.`. ```js assert(document.querySelectorAll('table')?.[1]?.querySelector('tbody')?.querySelectorAll('tr')?.[3]?.querySelector('th')?.innerText !== 'Total Liabilities.'); ``` </ins> Your `th` element should have the text `Total Liabilities`. ```js