Question: [types.setEditorFocusability]: (state, { payload }) => ({ ...state, canFocusEditor: payload <ins> }), [types.setAccessibilityMode]: (state, { payload }) => ({ ...state, inAccessibilityMode: payload </ins> }) }, initialState

Looking forward for reporting a security issue: Please report security issues by sending an email to instead of raising a Github issue. Describe the bug A clear and concise description of what the bug is. The Monaco editor contains features for accessibility, specifically a mode for screen reader users which helps in navigating and using the editor effectively. This feature, as of now, must be enabled at the start of each lesson, even after enabling it once at the beginning of the session. To Reproduce Steps to reproduce the behavior: to any lesson in the curriculum. the code editor, set focus to it. alt+f1 to show accessibility help for the editor, and choose to enable the screen reader mode the lesson, advance to the next, and repeat steps two and three Expected behavior A clear and concise description of what you expected to happen. The screen reader mode should have stayed enabled across lessons. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: [e.g. iOS] Windows Browser [e.g. chrome, safari] Chrome Version [e.g. 22] 69.0.3497.100 (Official Build) (64-bit) Smartphone (please complete the following information): Device: [e.g. iPhone6] OS: [e.g. iOS8.1] Browser [e.g. stock browser, safari] Version [e.g. 22] Additional context Add any other context about the problem here. Tested screen reader: NVDA version 2018.3.2 from
Hey, As a part of hacktoberfest, I would like to work on this issue. Can I expect mentorship on this?
I'm new on this too. But if you need help, I would like to work on this issue too.
Can you reproduce this issue?
A group of us are working on this issue for a class project in university. We aim to address this in the next couple of days. We will try and at least present the community with a first iteration of our proposed solution. Just a heads up. If the current developers have any advice or tips, feel free to contact me. Thank you. is the primary developer in the team, working alongside me.
Any updates on this ?
This looks to be fixed, the editor is focused on load.

Can you confirm that this is fixed If so, this can probably be closed.
I don't think it is fixed. It focuses on load by default, but I think that turning on the screen reader mode is separate from just focusing. I don't have a screen reader installed, but if I follow the steps above I keep having to re-enable that mode each time I go to a new challenge.
Sorry, I don’t think the editor should be focused on load, as that means the screen reader user most unfocus it, move back to the heading to read the challenge, then focus it again to write code. Also, I still have to enable accessibility mode on each challenge.
I see now. And I can say that the built in screen reader on osx doesn't do anything with the editor. Is this something we can control? Or is it just part of the monaco editor and we are at their mercy?
VoiceOver on MacOS is… not the best, sadly, when it comes to web apps. If possible, you can send technical info about this to <mailto: is Microsoft’s editor, which seems to be VSCode stripped down to the editor. Perhaps you could contact Microsoft and see if they could add a way to make accessibility states persistent across loads, if this isn’t possible already.
That is annoying. For now you should be able to focus the description by pressing escape (at the moment, it's still in a state of flux), but I'll see about making screen-reader mode something that persists between challenges.
Seeing as how this issue is beyond our control, should we close this and make a new issue about the editor being focused on load? You can feel free to email apple or microsoft if you want Thanks for the advice though.
no need to close this. I think I can fix it.
Yes, we can close this issue.
Quick update. Both the auto-focusing and the persistence of accessibility mode should be fixable. I think I'm about 90% of the way there, but for some reason it stops letting you toggle the accessibility support after a couple of toggles. This, obviously, isn't ideal, but most of the functionality is there.


Question: ## Solution: ```javascript let username = "JackOfAllTrades"; <del> let userCheck = /^[a-z]{2,}d*$/i; </del> <ins> const userCheck = /^[a-z]([0-9]{2,}|[a-z]+d*)$/i; </ins> let result = userCheck.test(username); ``` ## Explain: <del> 1. The only numbers in the username have to be at the end. `d$` There can be zero or more of them at the end. `*` ```javascript /d*$/; ``` 2. Username letters can be lowercase and uppercase. `i` ```javascript /d*$/i; ``` 3. Usernames have to be at least two characters long. `{2,}` A two-letter username can only use alphabet letter characters. `^[a-z]` ```javascript /^[a-z]{2,}d*$/i; ``` </del> <ins> 1. `^` - start of input 2. `[a-z]` - first character is a letter 3. `[0-9]{2,0}` - ends with two or more numbers 4. `|` - or 5. `[a-z]+` - has one or more letters next 6. `d*` - and ends with zero or more numbers 7. `$` - end of input 8. `i` - ignore case of input </ins>

Describe your problem and how to reproduce it: Solution to this challenge doesn't take into account that: Three-or-more-character usernames with a single alphabet letter character at the beginning are obviously the solution as well. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Browser Version: Version 71.0.3578.98 (Official Build) (64-bit) Operating System: Ubuntu Mate 16.04 LTS If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
I suggest this solution: Obviously, my solution uses positive lookahead (studied few challenges forward in the curriculum).
If my understanding is correct, from this description: "1) The only numbers in the username have to be at the end. There can be zero or more of them at the end." it sounds like you cannot mix letters and digits together. So if you have 3 or more letters, but only 1 at the beginning, that means that the rest have to be mixed with other numbers, and this is the reason is not covered in the solution. The fact that your solution passes, could be an issue in the test cases maybe. What do you think? I am willing to fix this once we can decide whether the description & solutions are wrong, or the test cases.
I mistakenly wrote letter instead of character in three-or-more-character. I corrected it. You can check my solution in a website like regexr with the examples of usernames. Thanks for showing interest!
This challenge was recently updated. The solution to the challenge file... This can be put in the guide.


Question: # --description-- <del> Create a `random` property. This property should use the first two numbers from an array to generate a random whole number. The range for this number starts at the smaller positive number (inclusive) among the first two numbers and ends just before the sum of these two numbers. Use the `Math.floor()` and `Math.random()` methods for the calculation. </del> <ins> Create a `random` property. This property should use the first two numbers from an array to generate a random whole number. The range for this number starts at the first number (inclusive) of the two and ends just before the sum of these two numbers. Use the `Math.floor()` and `Math.random()` methods for the calculation. </ins> # --hints--

The instructions for step 102 of the spreadsheet project (js beta) want us to "use the first two numbers from an array to generate a random whole number." They also say that "The range for this number starts at the smaller positive number (inclusive) among the first two numbers and ends just before the sum of these two numbers." However, looking at the solution, no effort is made to sort out which number is smallest before finding the random value. This tells me that this step is assuming we know that the array is in ascending sorted order. I would like the step to just say this explicitly. For eg it could say: Create a random property. This property should use the first two numbers from an array that has been sorted in ascending order to generate a random whole number. (the change is I said 'an array that has been sorted in ascending order') Or, we could just not care in what order the random number gets generated? (and change the instructions to say to get a random number between the first two numbers of the array regardless of which one goes first?) N/A instructions can be more explicit or checks can be more lenient No response N/A No response
I wrote about this also on discord - I'm not sure why the constraint to have the first number smaller. There's no reason to not allow first number to be higher than second one. Both will give number from different, valid ranges: -number from to . -number from to .
Yeah, I'd just update the text to say:


Question: If `myVal` is equal to `10`, the equality operator returns `true`, so the code in the curly braces will execute, and the function will return `Equal`. Otherwise, the function will return `Not Equal`. In order for JavaScript to compare two different <dfn>data types</dfn> (for example, `numbers` and `strings`), it must convert one type to another. This is known as Type Coercion. Once it does, however, it can compare terms as follows: ```js <del> 1   ==  1 1   ==  2 1   == '1' "3" ==  3 </del> <ins> 1   ==  1  // true 1   ==  2  // false 1   == '1' // true "3" ==  3  // true </ins> ``` <del> In order, these expressions would evaluate to `true`, `false`, `true`, and `true`. </del> # --instructions-- Add the equality operator to the indicated line so that the function will return the string `Equal` when `val` is equivalent to `12`.

The student has to go all the way down up to the explanation "In order, these expressions would evaluate to true, false, true, and true." to realize what the result of the operations is. My suggestion is that the second section of the code should look like this: 1 == 1 // true 1 == 2 // false 1 == '1' // true "3" == 3 // true instead of the screenshot attached. <!-- Add a link to the coding challenge with the problem. -- <!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --!
I would be fine with this change. Any interest in making a PR for it
, Can I? I don't know how to do it and I have never done it in my life, but besides that, I would like to do it by myself using some guide you could give me. I have never used GitHub in the past. And this will help me to contribute even more to this awesome project.
We have some . It may look a little intimidating, but if you follow the instructions it's not bad. The file where this needs to be fixed is Technically, you can edit the file on github and make a PR from there - which can work for some simple fixes, but you can't see and test your changes. I think we would accept those if you want to do that, but I would recommend setting the project up locally at some point if you want to contribute regularly. To be clear, we usually like to get second opinion before making changes like this - since we don't have that, I can't guarantee a PR would be merged - but I think others would be fine with the change so if you want to make a PR, go ahead.
This change seems good. For context, we got rid of a lot of comments since we'd need to translate them. However, these are keywords and don't need translation.
shall I take this up?
Could you clarify if this is actually what we wanted, because this is exactly what we removed 12 months ago in:
Yes, this is okay because these instances specifically are only keywords that don't get translated anyway.


Question: background-color: #c9d2fc; } <ins> --fcc-editable-region-- </ins> .cat-head { <del> --fcc-editable-region-- --fcc-editable-region-- </del> background: linear-gradient(#5e5e5e 85%, #45454f 100%); width: 205px; height: 180px; border: 1px solid #000; border-radius: 46%; } <ins> --fcc-editable-region-- </ins> ```

The active editor for step 9 is currently one empty line placed within the ruleset. Since the instructions above the editor are relatively long it makes it hard to see the selector, which has the potential to confuse people and cause them to unnecessarily add it again (I just dealt with a forum post that did this exact thing). In step 8 we have the active editor include the entire ruleset and leave a blank line for the new property to be . I would suggest we do the same thing for step 9, and leave three blank lines if possible since we are asking for three new properties to be . Step 10 and 11 also have a similar issue, but they are only changing the values of existing properties, so perhaps this is not as big an issue for those steps? I'm fine with keeping them as they are now. In the forum post the selector was again resulting in the following CSS: Have the active editor encompass the entire ruleset and leave three empty lines for the three new properties. No response N/A No response
Hey ! This change makes sense. I have looked through the forum and have seen the issue with campers getting confused. So it would be easy enough to fix. I will do a quick write up with the suggested changes and open it up for contribution I vote to leave steps 10 and 11 as they are for now, just because I haven't seen that pop up to much on the forum.
I am opening this up for first timer contributors since it is small fix. Please make sure to read the and first. Here is the file you will be working with You will need to change the editable region to include the entire ruleset It should produce this result which will make it clearer for campers what changes they will need to add. <img width="902" alt="Screenshot 2023-10-28 at 10 06 22 AM" src=""NOTE we do not assign issues. If you are interested in working on this, then read through the contributing docs and create a PR Happy contributing!
atempt


Question: 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--

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


Question: const buildProxyConsole = proxyLogger => ctx => { const oldLog = ctx.window.console.log.bind(ctx.window.console); ctx.window.console.log = function proxyConsole(...args) { <del> proxyLogger(args.map(arg => JSON.stringify(arg)).join(' ')); </del> <ins> proxyLogger(args.map(arg => '' + JSON.stringify(arg)).join(' ')); </ins> return oldLog(...args); }; return ctx;

Describe the bug Because the log calls and that returns , just outputs an empty line. This is in contrast to which outputs . To Reproduce Steps to reproduce the behavior: to into the editor. the tests Expected behavior


Question: This series of challenges introduces how to use Redux with React. In a React Redux app, you create a single Redux store that manages the state of your entire app. Your React components subscribe to only the pieces of data in the store that are relevant to their role. Then, you dispatch actions directly from React components, which then trigger store updates. <del> Improve this intro on [GitHub](https://github.com/freeCodeCamp/learn/tree/master/src/introductions/front-end-libraries/react-and-redux/index.md). </del>

Describe your problem and how to reproduce it: 1) Go to: 2) Find this text: "Improve this intro on GitHub." 3) Link to GitHub to improve the intro is broken Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: 79 Operating System: Mac OS 10.13.6 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !
I am not even sure why that last sentence is present. I think it is best if it is removed completely from the introduction. If you see anymore links like this, please add them to this issue, so someone can create a PR to fix them all at the same time.
What do you think about removing the link to the redux website (the first word in the intro)
I think for now, we can leave it alone. I think the discussion of external links should be on a separate issue (if there is not already an outstanding issue). I thought I had an open issue at one point about external links. It may have gotten closed at some point (can't remember why).
Hey guys , the same issue is happening in the React and Redux section, please check:


Question: - Fill in the usual HTML boilerplate. <del> - finally, add the following `h1` to the `body`: `<h1>Homepage</h1>` </del> <ins> - Finally, add the following `h1` to the `body`: `<h1>Homepage</h1>` </ins> ## Anchor Elements To create a link in HTML, you use the anchor element. An anchor element is defined by wrapping the text or another HTML element you want to be a link with an `<a>` tag.

The word "finally" should be capitalized. <img width="585" alt="Screenshot 2024-03-26 at 13 15 32" src=""- Capitalize the word "finally" in the following files:
This issue is open to first-time code contributors to this repository. The file that you should be updating is linked in the original post. Please make sure you read our as well as 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.
Here is the PR for the fix:


Question: ```js const sum = (x, y, z) => { const args = [x, y, z]; <del> return args.reduce((a, b) => a + b, 0); </del> <ins> let total = 0; for (let i = 0; i < args.length; i++) { total += args[i]; } return total; </ins> } ```

The challenge is using the method which hasn't been introduced yet. I believe it is an artifact of the current section order (ES6 now comes before functional programming). You don't really need to understand how works to solve the challenge but just to avoid any confusion it might be better to change it to use a simple for loop. The guide post will need to be updated as well if this change is made. Should not contain code that is unfamiliar to the student. 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] Forum post: Guide post:
hey i have fix this issue let you check PR


Question: You should give the `meta` tag a `charset` of `UTF-8`. ```js <del> assert.equal(document.querySelector('head > meta')?.getAttribute('charset'), 'UTF-8'); </del> <ins> assert.equal(document.querySelector('head > meta')?.getAttribute('charset')?.toLowerCase(), 'utf-8'); </ins> ``` # --seed--

The value for is case-insensitive. Not sure if I missed any, but here are case-sensitive ones I found. Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-accessibility-by-building-a-quiz Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-css-animation-by-building-a-ferris-wheel Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-intermediate-css-by-building-a-picasso-painting Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-responsive-web-design-by-building-a-piano Case sensitive curriculumchallengesenglish14-responsive-web-design-22learn-the-css-box-model-by-building-a-rothko-painting a lot Both are valid The value for should be case insensitive for all challenges. 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]


Question: var passedBonfireHash = !{JSON.stringify(bonfireHash)}; var challengeName = !{JSON.stringify(name)}; var started = Math.floor(Date.now() / 1000); <ins> var _ = R; </ins> .col-xs-12.col-sm-12.col-md-8 #mainEditorPanel form.code

the first line in the function says - it wont pass testing unless you change it to Browser Name: Firefox Browser Version: 60.0.1 Operating System: High Sierra ! <hr!
You don't have to it, but because of strict mode it does need to be declared with , , or .
so its missing the then?
That's how I would update it.

i am suspecting another small bug, the next challenge after succesful code run in Bonfire: Chunky Monkey actually points to itself


Question: * Case Covers - Contrary to what you read on the internet, keeping the case covers on the computer aids cooling. Absence of the case covers disrupts air flow and can actually increase the heat inside the case. Room ventilation - Locate the computer where it is neutral to the rooms environmental registers. Keep the computer away from room heaters or vents at all times. * Room placement - Locate the computer away from windows or areas of strong sunlight exposure. Placement in closets can also provide challenges to cooling. <del> * Placement next to other computers - Locating the computer away from other equipment allows air to flow in and out of the computer. Placement close to other equipment can constrict air flow and increase heat. </del> <ins> * Placement next to walls and other computers - Locating the computer away from other equipment allows cool, clean, air to flow in and out of the computer. Placement close to other equipment can constrict air flow and increase heat. Placement next to a wall may also lead to the exhaust ports being completely blocked off and consequently increase heat. </ins> [Wikipedia - Article on computer cooling](https://en.wikipedia.org/wiki/Computer_cooling)

<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Add a Link to the page with the problem: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !
I'm taking this


Question: border-radius: 5px; background-color: var(--yellow-light); border-color: var(--yellow-light); <ins> color: black; font-weight: bold; </ins> } button#confirm-donation-btn:active, button#confirm-donation-btn:active:focus, button#confirm-donation-btn:hover { <del> color: var(--secondary-color); </del> <ins> color: black; </ins> background-color: #f2ba38; border-color: #f2ba38; }

Looking forward for reporting a security issue: Please report security issues by sending an email to instead of raising a GitHub issue. Describe the bug The heights of the SVG files on the landing page vary, which causes the certification chart to look inconsistent. To Reproduce <img width="946" alt="zoomfloatingvideowindowandLearntoCode—ForFree—CodingCoursesforBusyPeople" src="https://user-"Desktop (please complete the following information): OS: Mac Browser: Chrome Version: Version 88.0.4324.96 (Official Build) (x86_64)
Hi Quincy, I let know about this already.
in min height, so should take care of it.


Question: 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); }

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 :)

Is your feature request related to a problem? Please describe. The activities count on the search bar in both /learn, and /news is different than /forum. Describe the solution you'd like A clear and concise description of what you want to happen. Fix the count on activities. Additional context Add any other context or screenshots about the feature request here. <img width="629" alt="Screen Shot 2020-05-11 at 23 27 55" src="https://user-"<img width="730" alt="Screen Shot 2020-05-11 at 23 27 39" src="https://user-"


Question: "Al usar el elemento span, puedes poner varios elementos juntos, e incluso darle diferentes estilos a partes diferentes del mismo elemento.", "Anida la palabra "love" en tu elemento "Things cats love" dentro de un elemento span. Luego, asigna a ese elemento span la clase text-danger para hacer que el texto sea rojo.", "Así es como lo harías con el elemento "Top 3 things cats hate":",  "<p>Top 3 things cats <span class = "text-danger">hate</span></p>"   "<p>Top 3 things cats <span class = "text-danger">hate:</span></p>"  ] }, {

[ ] Use Responsive Design with Bootstrap Fluid Containers [ ] Make Images Mobile Responsive [ ] Center Text with Bootstrap [ ] Create a Bootstrap Button [ ] Create a Block Element Bootstrap Button [ ] Taste the Bootstrap Button Color Rainbow [ ] Call out Optional Actions with Button Info [ ] Warn your Users of a Dangerous Action [ ] Use the Bootstrap Grid to Put Elements Side By Side [ ] Ditch Custom CSS for Bootstrap [ ] Use Spans for Inline Elements [ ] Create a Custom Heading [ ] Add Font Awesome Icons to our Buttons [ ] Add Font Awesome Icons to all of our Buttons [ ] Responsively Style Radio Buttons [ ] Responsively Style Checkboxes [ ] Style Text Inputs as Form Controls [ ] Line up Form Elements Responsively with Bootstrap [ ] Create a Bootstrap Headline [ ] House our page within a Bootstrap Container Fluid Div [ ] Create a Bootstrap Row [ ] Split your Bootstrap Row [ ] Create Bootstrap Wells [ ] Add Elements within your Bootstrap Wells [ ] Apply the Default Bootstrap Button Style [ ] Create a Class to Target with jQuery Selectors [ ] Add ID Attributes to Bootstrap Elements [ ] Label Bootstrap Wells [ ] Give Each Element a Unique ID [ ] Label Bootstrap Buttons [ ] Use Comments to Clarify Code
Working on this one


Question: # --description-- <del> You used the `inputVal` property as the `id` attribute for your paragraph elements. Now you can target those the paragraph elements with those `id`s. </del> <ins> You have set the `id` attribute for your paragraph elements to the `obj.inputVal` property. </ins> <del> Use the `.getElementById()` method to select the element with the `id` attribute with the value of the `inputVal` property of the current object. </del> <ins> Now, use `getElementById` to select the element with that attribute value, again using the `obj.inputVal` property. </ins> # --hints--

In the first paragraph, on the 2nd phrase, you can read: . Rectify to the following: No response . 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 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 suggest we remove "those" and keep "the" so we are not repeating "those". I would also suggest using "attribute value"
The next paragraph reads pretty bad as well. It's just confusing to read. Maybe we can come up with something better. Edit: take two Or something like that?
I know the first line already mentioned "paragraph elements", so it is presumed that the second line is referring to that type of element. But as a newbie, when I read "to select the element with that attribute value", it seems any kind of element. Could we be more specific, and edit to "(...) to select the paragraph element (...)"?
It is selecting by so the element type doesn't matter. Saying what the element type is seems redundant to me. But if you or anyone else feel it would make it more clear, then I wouldn't be opposed to it.
Yes, you are right. Mentioning is what matters.


Question: "" ], "solutions": [  "function myTest(val) {n  if(val > 10) {n    return "10 or Bigger";n  } else if(val < 5) {n    return "Smaller than 5";n  } else {n    return "Between 5 and 10";n  }n}"   "function myTest(val) {n  if(val > 10) {n    return "Greater than 10";n  } else if(val < 5) {n    return "Smaller than 5";n  } else {n    return "Between 5 and 10";n  }n}"  ], "tests": [ "assert(code.match(/else/g).length > 1, 'message: You should have at least two else statements');", "assert(code.match(/if/g).length > 1, 'message: You should have at least two if statements');",  "assert(myTest(0) === "Smaller than 5", 'message: myTest(4) should return "Smaller than 5"');", "assert(myTest(5) === "Between 5 and 10", 'message: myTest(5) should return "Smaller than 5"');",   "assert(myTest(0) === "Smaller than 5", 'message: myTest(0) should return "Smaller than 5"');", "assert(myTest(5) === "Between 5 and 10", 'message: myTest(5) should return "Between 5 and 10"');",  "assert(myTest(7) === "Between 5 and 10", 'message: myTest(7) should return "Between 5 and 10"');", "assert(myTest(10) === "Between 5 and 10", 'message: myTest(10) should return "Between 5 and 10"');",  "assert(myTest(12) === "10 or Bigger", 'message: myTest(12) should return "10 or Bigger"');"   "assert(myTest(12) === "Greater than 10", 'message: myTest(12) should return "Greater than 10"');"  ], "type": "waypoint", "challengeType": "1",

Return statement Issue: JS Line 3: Return statement text should be "Greater than 10" instead of "10 or bigger" Challenge Link : Browser Version : v47.0.2526.106 (64-bit) Operating System Version : Mac OS X 10.11.2 Steps to reproduce: to the above challenge link and check the text. (Optional)Read/Run the below test case in the above waypoint challenge page myTest(10) should return "Between 5 and 10" Screenshot 1: ! Screenshot 2: !
:+1: yes "10 or bigger" means
This same waypoint has some more minor bugs associated with it (in the test cases). They are : To save PR Reviewer time, I am merging this very minor issues in one and creating one commit to fix this.


Question: # --hints-- <del> You should have `if (next_empty := self.find_empty_cell()) is None:` withing `solver`. </del> <ins> You should have `if (next_empty := self.find_empty_cell()) is None:` within `solver`. </ins> ```js const tCode = code.replace(/r/g, '');

Typo on Step 61 of Sudoku Solver project in Scientific Computing with Python (Beta) cert: "withing" in the hint text when I'm sure you meant "within". <img width="595" alt="Screen Shot 2024-03-21 at 1 39 54 PM" src=""Thanks for all the content!
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.


Question: display: flex; justify-content: center; align-items: center; <del> background: lightblue; </del> }

To Reproduce Steps to reproduce the behavior: to /learn or /settings with the theme set to dark off internet connection and wait Actual behavior The offline warning message shows up, but the text is quite hard to read. Screenshots <img width="1680" alt="Screen Shot 2020-11-09 at 12 22 16 AM" src="https://user-"
WCAG does say the contrast is only 1.41:
The notification background is hardcoded and the font color is being handled based on theme. We have let bootstrap handle the styling for the notifications since they handle the font color and the background and look well on both themes. So doing the followings should do the trick. Add as a class here: and remove the from here:
I think the best way is to implement luma-corrected calculations. The first obvious implication of going with a luma-corrected approach is that the notification background color needs to switch to an RBG declaration for the backgrounds, calculate the luma from whatever method we choose, and use it on the foreground color declaration, which can (and will) still be HSL color. I am saying this because this would allow the font color to switch based on the contrast of the notification background contrast from to and vice versa.
can I work on this? I might need help. please guide me.
that is a cool trick. Thanks for sharing the link. Since are planning to move off of bootstrap, we should consider luma-corrected calculations in how we implement our dark/light themes during the rewrite process. Meanwhile, I think we could move forward with making the simple change that resolves this issue. sure. Make sure you read this:


Question: ```yml tests: - text: Traditional function expression should not be used.  testString: getUserInput => assert(!getUserInput('index').match(/function/));   testString: getUserInput => assert(!removeJSComments(code).match(/function/));  - text: setGear should be a declarative function.  testString: getUserInput => assert(typeof bicycle.setGear === 'function' && getUserInput('index').match(/setGears*(.+)s*{/));   testString: assert(typeof bicycle.setGear === 'function' && code.match(/setGears*(.+)s*{/));  - text: bicycle.setGear(48) should change the gear value to 48. testString: assert((new bicycle.setGear(48)).gear === 48);

<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: I commented out the code and then followed the new syntax for the challenge, but because the commented out code had normal function declaration it didn't pass. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Google Chrome Operating System: Mac OS High Sierra If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): // change code below this line const bicycle = { gear: 2, setGear(newGear) { "use strict" = newGear } } / const bicycle = { gear: 2, setGear: function(newGear) { "use strict"; = newGear; } }; // change code above this line bicycle.setGear(3); (); /
Hi, We used regex to match "function" keyword in the code but this instance can be fixed. I'll take a stab at it.
I think this issue occurs with a lot of the challenges. For an example, and Can a statement just be left in the description saying to not use the keyword even as a comment?
A better way is how we solved other such problems. We stripped all the comments out with a regular expression and then validated the user did not use what they were not supposed to. I just created PR to fixed this issue,


Question: assert(code.match(/htmls*>/gi)); ``` <ins> Your `DOCTYPE` declaration should be at the beginning of your HTML. ```js assert(__helpers.removeHtmlComments(code).match(/^s*<!DOCTYPEs+htmls*>/i)); ``` </ins> # --seed-- ## --seed-contents--

Several. One example is The hint for this step seems to indicate that the user must add the element below the (there must be at least one new line separating them). Hint: "Your element should be below the declaration.:" So the expected behavior would be that the user will not pass this step until they add the element below the . <!-- Please complete the following information. --- Device: Desktop OS: Linux/Fedora 34 Browser: Firefox Version: [e.g. 22] This is happening for several courses. The regex used for this test is not enforcing the newline between the elements. If this requirement is important enough to be enforced then we should probably come up with one regex that enforces this requirement and use it for all courses.
One possible regex I am using as a solution for this is:
Affected pages: : js 57 assert((/^s<!DOCTYPEs+htmls[sS]<shtmls/gi)); 58 : js 55 assert((/(?<!<htmls)<!DOCTYPEs+htmls/gi)); 56 : js 53 assert((/(?<!<htmls)<!DOCTYPEs+htmls/gi)); 54 : js 55 assert((/(?<!<htmls)<!DOCTYPEs+htmls/gi)); 56 : js 17 assert((/(?<!<htmls)<!DOCTYPEs+htmls/gi)); 18 : js 17 assert((/(?<!<htmls)<!DOCTYPEs+htmls/gi)); 18 : js 41 assert((/(?<!<htmls)<!DOCTYPEs+htmls/gi)); 42 : js 53 assert((/(?<!<htmls)<!DOCTYPEs+htmls*/gi)); 54
If the regex from is the way we want to go, I'd be happy to start working on it in the pages linked by .
I was eventually going to get around to updating these but please, feel free to step in. My solution above was officially merged into main so I'm assuming that's acceptable to use for these as well.
I'm beginning to wonder if we should even have a requirement that the DOCTYPE be on its own separate line?

I can't seem to find any documentation that says this is required and the W3C HTML validator accepts it without being on a new line. Also, we don't seem to be enforcing separate lines for other types of tags. But the DOCTYPE does need to be the first element on the page, which I don't think we are currently testing for, so I propose we test for that instead and get rid of the separate line requirement.
As far as the tests go, I suggest we stick with this: If the HTML spec can parse it, it is valid, and should be accepted, unless the instructions specifically say, for example, "add a semi-colon at the end of the value" So, as I can see in the spec, there is no requirement for the DOCTYPE and the element to be on separate lines:
Would you agree with me then that instead of testing for DOCTYPE being on a separate line we should be testing that the DOCTYPE is the first element on the page? This brings us back to another I found in which there are JS comments in the code string before the HTML begins: Not impossible to work around, just wanted to make whoever ultimately works on this aware of it.
It wouldnt surprise me if that's the why the test was written that way, because if doctype isnt the first element, how else would you check it's current placement? It would be in relation to the html tag, right?
Ideally, yes. As I mentioned below, we do have a solution to the comment thing, but it is a work-in-progress.
I have submitted a that fixes the source of this issue (css comments before the html in the code string) which if approved will allow us to easily test that the DOCTYPE declaration is the first element in the HTML.
should i close my initial pull request since you said in your pull request that you were going to fix the others once yours gets approved and merged? I dont mind helping update the other docs with the new test once it's approved if you want me to. either way, just let me know !
We've had a couple of reports in the support inbox that the negative lookbehind used in some of these tests is failing in Safari, so it's great that either or (pending update) will take care of that as well. At the moment seems more flexible, and allows valid code to pass without forcing a particular style.

It'll also be good to move away from regex for this type of test.
If __helpers.removeHtmlComments(code) is preferred, we could modify in that direction or accept alternatively.
Yes, is the final PR to put this issue to rest. I did an initial PR for just one course and it has already been merged. is using the same solution, just updating the remaining courses that need it.


Question: console.log(obj); ``` <del> The `obj.review` and `obj.newProp` assignments will result in errors, and the console will display the value `{ name: "FreeCodeCamp", review: "Awesome" }`. </del> <ins> The `obj.review` and `obj.newProp` assignments will result in errors, because our editor runs in strict mode by default, and the console will display the value `{ name: "FreeCodeCamp", review: "Awesome" }`. </ins> # --instructions--

At the top, the challenge says, " Any attempt at changing the object will be rejected without an error." A few lines later it says, "The and obj.newProp assignments will result in errors". This seems to be conflicting information - will there be an error or not? Maybe the 2nd part should say "The and obj.newProp assignments will be rejected". !
Oddly, when I run the tests I can see an error in the log: [TypeError: Cannot assign to read only property 'PI' of object '#<Object'] But when I run the same code in jsFiddle there is no error in the console. Update: When I add "use strict" in jsFiddle I get an error. This challenge should definitely mention that you only get an error in strict mode! One of the previous challenges about "let" and "const" mention strict mode briefly, but it might be good to explain strict mode more. This page was helpful:
I do agree that some clarification here would be beneficial. Possibly changing that first line to `Any attempt at changing the object will be rejected, with an error thrown if the script is running in strict mode. And the second line being Thoughts?
That seems like a good solution Nich, I'll put a help wanted label on it!


Question: ```js const borderBottom = new __helpers.CSSHelp(document).getStyle('fieldset:last-of-type')?.borderBottom; <del> assert(borderBottom === 'none' || borderBottom === 'medium none'); </del> <ins> assert(borderBottom === 'none' || borderBottom === 'medium none' || borderBottom === 'medium'); </ins> ``` # --seed--

I've come across two forum posts from Safari users in the past few days saying that they can't pass step 47 even though their CSS is correct. Based on the hint they are getting, the test that is not passing is: I'm wondering if Safari has recently changed the string being returned for the border properties when set to ? I don't have a mac so I can't test this for myself. Opening this issue with the hopes that a Safari user can figure out what is going on here. Should be tested on a very recent version of Safari. This is the correct CSS but it is apparently not passing for Safari users. Correct CSS should pass. No response For both posters, user agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.4 Safari/605.1.15 No response


Question: } </style>       ```

We need to replace all images and audio samples for the legacy content with the ones that were just to our freeCodeCamp cdn. Here are all of the files that will need to be updated Here are all of the new asset links


Question: ```js assert.strictEqual( (function () { <del> bob.setFullName('Haskell Curry'); return bob.getLastName(); </del> <ins> _test_bob.setFullName('Haskell Curry'); return _test_bob.getLastName(); </ins> })(), 'Curry' );

A user can fail with correct code because the tests secretly rely upon global variables accessible to the user. This code fails because the user has the correct solution but deleted the instantiation of the object. Tests should instantiate any data they need. We should update the seed code to We should then add and modify the test suite to use instead of . No response All No response
Hello, Just to clarify, did you want to add in the user code block? Because I noticed when I attempted to reproduce the bug you encountered that two test cases still passed, despite not being initialized in the user's code. I checked the lesson's markdown file and found out that those two test cases did have their own initialized. I was thinking of adding to all the test cases instead. For reference, here's the code for one of the test cases that still passed, despite the bug.
Those tests initiate their own values so they are fine. I'm talking about the tests that fail if users modify their seed code to not have the object initialization. The new variable would go into a new --after-user-code-- part; that's not currently present. Just adding this new variable inside of the seed creates the exact same problem. Note - this issue isn't marked as ready for contributions yet. Maybe we should review if the tests logic too to see if they are independent
Opening this up for contribution.
Hi assign this issue for branch bugfix/. I have resolved it, need to create PR for same
We don't assign issues. The first PR that fully covers the issue will be accepted.
Hi ok !! I have raised PR . thanks for reply.


Question: isModalShowing = !isModalShowing; if (isModalShowing) { <del> rulesBtn.textContent = "Hide Rules"; </del> <ins> rulesBtn.textContent = "Hide rules"; </ins> rulesContainer.style.display = "block"; } else { <del> rulesBtn.textContent = "Show Rules"; </del> <ins> rulesBtn.textContent = "Show rules"; </ins> rulesContainer.style.display = "none"; } });

Initial text of the button is . After step clicking button is expected to change text to , capitalizing the second word. Clicking it again is expected to change text to . Which is too differing from initial capitalization. n/a Capitalization should be consistent throughout the project. Either Show rules and Hide rules; or Show Rules and Hide Rules. No response n/a No response
We will do this option


Question: this.props.setEditorFocusability(false); } }); <ins> this._editor.addAction({ id: 'toggle-accessibility', label: 'Toggle Accessibility Mode', keybindings: [monaco.KeyMod.CtrlCmd | monaco.KeyCode.F1], run: () => { const currentAccessibility = this.props.inAccessibilityMode; // The store needs to be updated first, as onDidChangeConfiguration is // called before updateOptions returns this.props.setAccessibilityMode(!currentAccessibility); this._editor.updateOptions({ accessibilitySupport: currentAccessibility ? 'auto' : 'on' }); } }); </ins> this._editor.onDidFocusEditorWidget(() => this.props.setEditorFocusability(true) ); <ins> // This is to persist changes caused by the accessibility tooltip. // Unfortunately it relies on Monaco's implementation details this._editor.onDidChangeConfiguration(() => { if ( this._editor.getConfiguration().accessibilitySupport === 2 && !this.props.inAccessibilityMode ) { this.props.setAccessibilityMode(true); } }); </ins> }; focusOnHotkeys() {

Looking forward for reporting a security issue: Please report security issues by sending an email to instead of raising a Github issue. Describe the bug A clear and concise description of what the bug is. The Monaco editor contains features for accessibility, specifically a mode for screen reader users which helps in navigating and using the editor effectively. This feature, as of now, must be enabled at the start of each lesson, even after enabling it once at the beginning of the session. To Reproduce Steps to reproduce the behavior: to any lesson in the curriculum. the code editor, set focus to it. alt+f1 to show accessibility help for the editor, and choose to enable the screen reader mode the lesson, advance to the next, and repeat steps two and three Expected behavior A clear and concise description of what you expected to happen. The screen reader mode should have stayed enabled across lessons. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: [e.g. iOS] Windows Browser [e.g. chrome, safari] Chrome Version [e.g. 22] 69.0.3497.100 (Official Build) (64-bit) Smartphone (please complete the following information): Device: [e.g. iPhone6] OS: [e.g. iOS8.1] Browser [e.g. stock browser, safari] Version [e.g. 22] Additional context Add any other context about the problem here. Tested screen reader: NVDA version 2018.3.2 from
Hey, As a part of hacktoberfest, I would like to work on this issue. Can I expect mentorship on this?
I'm new on this too. But if you need help, I would like to work on this issue too.
Can you reproduce this issue?
A group of us are working on this issue for a class project in university. We aim to address this in the next couple of days. We will try and at least present the community with a first iteration of our proposed solution. Just a heads up. If the current developers have any advice or tips, feel free to contact me. Thank you. is the primary developer in the team, working alongside me.
Any updates on this ?
This looks to be fixed, the editor is focused on load.

Can you confirm that this is fixed If so, this can probably be closed.
I don't think it is fixed. It focuses on load by default, but I think that turning on the screen reader mode is separate from just focusing. I don't have a screen reader installed, but if I follow the steps above I keep having to re-enable that mode each time I go to a new challenge.
Sorry, I don’t think the editor should be focused on load, as that means the screen reader user most unfocus it, move back to the heading to read the challenge, then focus it again to write code. Also, I still have to enable accessibility mode on each challenge.
I see now. And I can say that the built in screen reader on osx doesn't do anything with the editor. Is this something we can control? Or is it just part of the monaco editor and we are at their mercy?
VoiceOver on MacOS is… not the best, sadly, when it comes to web apps. If possible, you can send technical info about this to <mailto: is Microsoft’s editor, which seems to be VSCode stripped down to the editor. Perhaps you could contact Microsoft and see if they could add a way to make accessibility states persistent across loads, if this isn’t possible already.
That is annoying. For now you should be able to focus the description by pressing escape (at the moment, it's still in a state of flux), but I'll see about making screen-reader mode something that persists between challenges.
Seeing as how this issue is beyond our control, should we close this and make a new issue about the editor being focused on load? You can feel free to email apple or microsoft if you want Thanks for the advice though.
no need to close this. I think I can fix it.
Yes, we can close this issue.
Quick update. Both the auto-focusing and the persistence of accessibility mode should be fixable. I think I'm about 90% of the way there, but for some reason it stops letting you toggle the accessibility support after a couple of toggles. This, obviously, isn't ideal, but most of the functionality is there.


Question: "nameEs": "Usa appendTo para mover elementos con jQuery", "descriptionEs": [ "Ahora intentemos mover elementos de un div a otro.",  "jQuery tiene una función llamada appendTo() que le permite seleccionar elementos HTML y anexarlos a otro elemento.",   "jQuery tiene una función llamada appendTo() que te permite seleccionar elementos HTML y anexarlos a otro elemento.",  "Por ejemplo, si quisiéramos mover target4 de nuestro pozo (well) derecho a nuestro pozo izquierdo, usaríamos:", "$("#target4").appendTo("#left-well");", "Mueve tu elemento target2 de tu left-well a tu right-well."

[x] Learn how Script Tags and Document Ready Work [x] Target HTML Elements with Selectors Using jQuery [x] Target Elements by Class Using jQuery [x] Target Elements by ID Using jQuery [x] Delete your jQuery Functions [x] Target the same element with multiple jQuery Selectors [x] Remove Classes from an element with jQuery [x] Change the CSS of an Element Using jQuery [x] Disable an Element Using jQuery [x] Change Text Inside an Element Using jQuery [x] Remove an Element Using jQuery [x] Use appendTo to Move Elements with jQuery [x] Clone an Element Using jQuery [x] Target the Parent of an Element Using jQuery [x] Target the Children of an Element Using jQuery [x] Target a Specific Child of an Element Using jQuery [x] Target Even Numbered Elements Using jQuery [x] Use jQuery to Modify the Entire Page
Checking


Question: } pairedWith = pairedWith.pop(); <del> //debug('This is paired with', Object.keys(pairedWith)); debug('This is paired with's uncompleted bonfires array', pairedWith.uncompletedBonfires); </del> index = pairedWith.uncompletedBonfires.indexOf(bonfireHash); if (index > -1) { pairedWith.uncompletedBonfires.splice(index,1)

<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --The test requires a multi-line comment of the form . However, the test fails if additional ` characters are present at the beginning or the end of the text contained within the comment. Some examples : The regular expression for the corresponding test needs to be updated. Browser Name: Google Chrome Browser Version: 60+ Operating System: Ubuntu 18.04 !
Hi, I would like to have a go to fix this problem
That's good, please read .
Test fails if multiline style comment includes either / File: Line: 33 this regex is the problem

When I attempt to Run the tests for the code I submitted for Roman Numerals Converter, the page freezes and I cannot solve the issue until I clear the cashe of my browser. Help!
I have the same issue. My browser complains about a long running script and then bails out.
Ok, I figured this one out... if you use the solution in the Gritter chat, that solution will cause a never ending loop, because of the while expression (while numCopy 0 - which is always true btw). This never ending loop will freeze your browser. Moreover, as I lately discovered, the solution there only covers very few of the cases that we need to test to pass the Bonfire. So back to the drawing board, people!
Leaving this open as a bug for someone to fix the solution in the wiki to one that works with the new test cases.


Question: assert.match(afterCalculateTotal, /consts+taxs*=/); ``` <del> Assign the value of calling your new `.calculateTaxes()` method, passing `subTotal` as the argument, to the `tax` variable. </del> <ins> Assign the value of calling your new `.calculateTaxes()` method, passing `subTotal` as the argument, to the `tax` variable. Remember to use the `this` keyword. </ins> ```js const afterCalculateTotal = code.split('calculateTotal')[1];

When working through the , mentions the following: And when passing the following solution: This hint shows up: This doesn't pass because is expecting the following: I think adding the hint "Remember to use the keyword." is a valid hint, just like in when the keyword is not in the solution. It may be repetitive, but I think the user should be informed for this possible mistake. It's already in other steps anyway. When passing the incorrect code from the above, add the "Remember to use the keyword." hint and validation. No response Device: Laptop OS: macOS 13.6.6 Browser: Chrome Version: 124 No response
We can open this up to since this is a small change This has been opened 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 Change the last hint to be the following Happy coding
I can do it!


Question: Your new `div` should be empty. ```js <del> assert.equal(document.querySelector('.container > div')?.innerHTML, ''); </del> <ins> assert.equal(document.querySelector('.container > div')?.innerHTML.trim(), ''); </ins> ``` # --seed--

This step for checking an empty div element is to strict. This answer should be valid but fails the current test The tests only pass with this answer which is to restrictive The last test here needs to be updated to make it account of spacing. Probably using with a regex will be better then here Please read through the first We do not assign issues. If you are interested in working on this, please fix the test mentioned and create a PR Here is the file you will need to change Happy coding! This answer should be valid but fails the current test This answer should pass the tests 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


Question: ], "tests": [ "assert(editor.match(/$(.*button/g), 'Use the $&#40"button"&#41 selector.')",  "assert(editor.match(/$(.*.btn/g), 'Use the $&#40".btn"&#41 selector.')",   "assert(editor.match(/$(.*.btn/g), 'Use the $&#40".btn"&#41 selector.')",  "assert(editor.match(/$(.*#target1/g), 'Use the $&#40"#target1"&#41 selector.')", "assert(editor.match(/addClass/g) && editor.match(/addClass/g).length > 2, 'Only add one class with each of your three selectors.')", "assert($("#target1").hasClass("animated") && $("#target1").hasClass("shake") && $("#target1").hasClass("btn-primary"), 'Your #target1 element should have the classes animated‚ shake and btn-primary.')",

Challenge has an issue. With this code It validate the task "Use the (".btn").
Created PR


Question: ].concat(trusted), frameSrc: [ '*.gitter.im', <ins> '*.gitter.im https:', </ins> '*.vimeo.com', '*.twitter.com', '*.rafflecopter.com',

Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
methods are case sensitive. should be is a great place for questions like this
thanks for the issue but if you get stuck or have questions with a challenge in the future, please first ask questions to the . What has suggested is correct. Happy coding!
I've tried it several times, making sure code was acurate... there must be another problem
Sorry about that but no one was answering me in the help room
no worries. Yeah, sometimes the Help Rooms are pretty busy and getting help is difficult. Please be patient. There are many people in there that are willing to help. You can always tag me there and I get help you out when I can


Question: --- 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

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.


Question: <Col sm={10} smOffset={1} xs={12}> <Spacer /> <h1 className='text-center big-heading'> <del> {name ? 'Welcome back ' + name : 'Welcome to freeCodeCamp.org'} </del> <ins> {name ? 'Welcome back, ' + name + '.' : 'Welcome to freeCodeCamp.org'} </ins> </h1> </Col> </Row>

We should make this more grammatically correct by adding a comma and space before the name, and a period after it. For example: Welcome back, Quincy Larson. <img width="1405" alt="Learn_freeCodeCamp_org" src="https://user-"


Question: ], "tests": [ "assert($("body").css("background-color") === "rgb(0, 0, 255)", 'Give your body element the background-color of blue.')",  "assert(editor.match(/#0000FF/g) && editor.match(/#0000FF/g).length > 0, 'Use the hex code for the color blue instead of the word blue. For example body { color: #0000FF; }.')"   "assert(editor.match(/#0000FF/ig) && editor.match(/#0000FF/ig).length > 0, 'Use the hex code for the color blue instead of the word blue. For example body { color: #0000FF; }.')"  ], "challengeSeed": [ "

! Same with the other waypoints that ask for a hex code that includes alpha chars.
Green worked fine.. blue has case issue.


Question: import { tap, mapTo } from 'rxjs/operators'; import { transformEditorLink } from '../utils'; import envData from '../../../../../config/env.json'; <ins> import i18next from 'i18next'; </ins> const { forumLocation } = envData;

We want to localize the Ask-To-Help template that pre-fills the post on the forum. ! The above button which takes you to the forum should render this template: ! In the localized version instead.
Should be able to tackle this today, I think.
Sure. Not a high priority, so take your time.


Question: Finally, you need to make the `#output` element visible so the user can see your text. Your `output` variable is an Element, which has a `classList` property. This property has a `.remove()` method, which accepts a string representing the class to remove from the element. <del> Use the `.remove()` method of the `output` variable's `classList` property to remove the `hide` class. Don't forget to place the word `hide` inside quotes. </del> <ins> ```js const paragraphElement = document.getElementById('paragraph'); paragraphElement.classList.remove('hide'); ``` Use the `.remove()` method of the `output` variable's `classList` property to remove the `hide` class. Don't forget to place the word `hide` inside quotes. </ins> # --hints--

We should add a code example for the remove method in step 85. js const paragraphElement = document.getElementById('paragraph'); ('hide'); ` see explanation above see explanation above 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
This has been opened 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 Happy coding
Can we make this a issue?
Normally this would be a first timers only issue. But I already opened a tons of those earlier, that are still up for grabs. So I decided to make this one help wanted, to open it up to more people. Plus we still have those pretty earlier on that made one contribution but are still looking for easier issues to keep contributing.


Question: You should have a condition that checks if the left key was pressed and if `isCheckpointCollisionDetectionActive` is true. ```js <del> assert.match(code, /ifs*(s*keys.rightKey.presseds*&&s*isCheckpointCollisionDetectionActives*)s*{s*platforms.forEach(s*((s*platforms*)|platform)s*=>s*{s*platform.position.xs*-=s*5s*;s*}s*)s*;?s*}s*elses+ifs*(s*keys.leftKey.presseds*&&s*isCheckpointCollisionDetectionActives*)s*{.*}s*)s*;?/s); </del> <ins> assert.match(code, /ifs*(((s*keys.rightKey.presseds*&&s*isCheckpointCollisionDetectionActives*)|(s*isCheckpointCollisionDetectionActives*&&s*keys.rightKey.presseds*)))s*{s*platforms.forEach(s*((s*platforms*)|platform)s*=>s*{s*platform.position.xs*-=s*5s*;s*}s*)s*;?s*}s*elses+ifs*(((s*keys.leftKey.presseds*&&s*isCheckpointCollisionDetectionActives*)|(s*isCheckpointCollisionDetectionActives*&&s*keys.leftKey.presseds*)))s*{.*}s*)s*;?/s); </ins> ```

step 78 of the platformer game project wants the user to type: but if we type the checks in reverse like: It is not accepted. Stumbled on this one because to me writing the long variable name first is easier because I copy and paste it directly from the step and then I spend a little longer looking up how to tell the right key is pressed so I put that second. Since the order of conditions is not specified though in the step, the check should not be so picky. (see above) less strict checking when the order of comparisons in the if makes no difference to the result (or please specify that order matters in the instructions or the hint) No response N/A please note that step 80 has the same issue as well:


Question: assert.match(code, /consts+addOrUpdateTasks*=s*(s*)s*=>s*{s*consts+dataArrIndexs*=s*taskData.findIndex(s*(?:(s*items*)|item)s*=>s*(?:item.ids===s*currentTask.id|currentTask.ids*===s*item.id)s*)s*;?s*consts+taskObjs*=s*{s*ids*:s*`${s*titleInput.value.toLowerCase(s*).split(s*('|")s{1}1s*).join(s*('|")-2s*)s*}-${s*Date.now(s*)s*}`s*,s*titles*:s*titleInput.value,s*dates*:s*dateInput.values*,s*descriptions*:s*descriptionInput.values*,?s*}s*;?/) ``` <del> You should move the `if` statement with the condition `dataArrIndex === 1` into your `addOrUpdateTask` function. </del> <ins> You should move the `if` statement with the condition `dataArrIndex === -1` into your `addOrUpdateTask` function. </ins> ```js assert.match(code, /consts+addOrUpdateTasks*=s*(s*)s*=>s*{s*consts+dataArrIndexs*=s*taskData.findIndex(s*(?:(s*items*)|item)s*=>s*(?:item.ids*===s*currentTask.id|currentTask.ids*===s*item.id)s*)s*;?s*consts+taskObjs*=s*{s*ids*:s*`${s*titleInput.value.toLowerCase(s*).split(s*('|")s{1}1s*).join(s*('|")-2s*)s*}-${s*Date.now(s*)s*}`s*,s*titles*:s*titleInput.value,s*dates*:s*dateInput.values*,s*descriptions*:s*descriptionInput.values*,?s*}s*;?s*ifs*(s*dataArrIndexs*===s*-1s*)s*{s*taskData.unshift(s*taskObjs*)s*;?s*}s*}s*;?/)

In step 30, we refactor the code a bit by splitting up code we already wrote into functions. One of the statements to move is an if statement which checks the result of a findIndex function on an array. I forgot to mark the if statement in my cut-paste job and got the following note when checking the code: Unfortunately the condition in the note is completely wrong as the condition we want is to check if it's equal to -1 as that is the flag the findIndex function returns if it doesn't find a match. If the return value was 1, that's the id and we'd not want to enter the if statement. It's only the note which is wrong, and if I enter if (dataArrIndex === 1) { taskData.unshift(taskObj); } in the code, then I still have the note when checking the code, and only the actual correct if statement of equalling -1 lets me continue. But I'm sure such a situation could be frustrating for a camper if they write what's in the note and stay stuck To not accept the code and display a note saying the if condition should be ! Device: VivioBook ASUS Laptop OS: Windows 11 Home Browser: Mozilla Firefox 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 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.
Thank you. I tried to fix it in the repository. Hope I did it properly :)
I see that you made a commit to your forked copy of the project here <img width="416" alt="Screenshot 2024-02-08 at 4 10 12 PM" src=""But I don't see any new pull requests opened by you. Please read through the to learn how to make a pull request. If you need help, then please post on either the forum or discord with your question and people can assist you there


Question: assert(document.querySelector('.daily-value.small-text')?.lastElementChild?.querySelectorAll('span')?.length === 3); ``` <del> A `span` element should wrap the text `Sodium 360mg`. </del> <ins> A `span` element should wrap the text `Sodium 160mg`. </ins> ```js assert(document.querySelector('.daily-value.small-text')?.lastElementChild?.firstElementChild?.innerText?.match(/Sodium[s|n]160mg/));

The hint text for one of the tests in step 54 of the Learn Typography By Building a Nutrition Label project has a minor typo. This typo isn't visible unless a learner fails a specific test. The hint text currently reads "A element should wrap the text ". It should be updated to "A element should wrap the text " to match the instructions for this step, and the test itself. This would be a great first PR for new contributors.
I will be working on it.
why cloning the repo is throwing errors? I have been trying for 52 minutes
Add Newly generated SSH key from your device to your github account then clone
The problem is not with SSH key as half of the repo gets cloned and other gets skipped or deleted. The repo is too large to get cloned, I tried increasing buffer size but it didn't worked. Have you tried cloning it? Cloning depth wise might help but problem could be different if it is only appearing in my machine.
I just forked the main branch of the repository on my account and then git cloned that repository on to my local machine.


Question: bsStyle='primary' className='btn-link' onClick={closeDonationModal} <ins> tabIndex='0' </ins> > {closeLabel ? 'Close.' : 'Ask me later.'} </Button>

Describe the bug The popup modal for becoming a sponsor cannot be closed by just using the keyboard. To Reproduce Steps to reproduce the behavior: some challenges which triggers the modal Expected behavior The modal closes when pressing the Esc key The modal closes when clicking somewhere outside of the modal I can navigate to the "Ask me later" button with the tab key to close the modal Screenshots ! Desktop (please complete the following information): OS: Ubuntu Browser: chrome and firefox Version: Latest Smartphone (please complete the following information): Unknown
This is by design to the best of my knowledge. I would defer to Quincy for a confirmation.
Thanks for reporting that the "ask me later" link should be accessible by tab but you're correct - it isn't. We will fix this. We decided not to have escape key / clicking outside of the modal to dismiss this modal (like we do with other modals) since the goal is to get people to actually slow down and consider donating to our nonprofit - not to just mash the escape key.


Question: isOpen: true }); <del> if (files) { </del> <ins> if (files?.length) { </ins> return ( <button className='project-link-button-override'

I'm not sure if this was deliberately at some point, I'm guessing not - but viewing a cert solution for any cert brings up the JS code viewer with the URL in it when a URL is used to submit the project... ! Go View a solution See modal Possibly from this recent PR: - I swear I tested it
My bad. This line probably needs to change:
I just tried implementing your solution, but then realized I didn't know how to test if it worked without sign in/user data. How should that be done?
You should be able to log in - assuming the is set to true in your .env file. Then you can submit some projects, many of them can just be a URL and don't have any requirements. I believe the responsive web design, front end libraries, and data visualization don't require passing tests. So you should be able to get a cert like that and then go view it.
Turns out that login/the dev user doesn't work on my machine for some reason. Works fine on GitPod though, so it's been tested there.


Question:
In this section, you'll see how adding CSS styles to the elements of your CatPhotoApp can change it from simple text to something more.

 Note: Some browser extensions may interfere with elements on the page. If the tests fail, try disabling your extensions for the most reliable experience.

On , there should be a note displayed between the description and the buttons, but we are seeing an empty div instead: <img width="792" alt="Screenshot 2024-05-24 at 22 53 18" src=""The issue is due to the class to the . In Remove the class to make the note show up Remove the class as it is unused
This issue is open for contribution. Please make sure you read our as well as 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.


Question: That worked, but there is still a little space on the right of the price. <del> You could keep trying various percentages for the widths. Instead, use the back space key on your keyboard to move the `p` element with the class `price` next to the `p` element with the class `flavor` so that they are on the same line in the editor. Make sure there is no space between them. </del> <ins> You could keep trying various percentages for the widths. Instead, use the back space key on your keyboard to move the `p` element with the class `price` next to the `p` element with the class `flavor` so that they are on the same line in the editor. Make sure there is no space between the two elements. </ins> # --hints--

In the directions for the challenge it states "Instead, use the back space key on your keyboard to move the p element with the class price next to the p element with the class flavor so that they are on the same line in the editor. Make sure there is no space between them". But here's the thing, to some campers it might be unclear that the 'them' in the second sentence refers to the elements, and might assume it means the class attribute or something. While this is addressed in the hint, it probably should be clearer in the challenge directions. In this challenge, it should be clear that the last sentence refers to the spacing between the two elements. No response Device: Desktop OS: Windows 10 Browser: Firefox Version: 123.0.1 I've seen at least two threads on the forums covering this challenge.


Question: "descriptionEs": [ [ "http://i.imgur.com/tP2ccTE.gif", <del> "Un gif mostrandore como puedes pulsar en tu imagen de perfil en la esquina superior derecha conectar tu portafolio y GitHub.", "Dale un vistazo de tu portafolio de código. Da click en tu imagen en la esquina superior derecha. Para activar tu portafolio de código, necesitaras conectar tu cuenta de GitHub con Free Code Camp. Tu portafolio de código muestra tu progreso y cuantos Brownie Points tienes. Puedes obtener Brownie Points completando desafíos y ayudando a otros campistas en nuestras salas de chat. Si obtienes Brownie Points varios días consecutivos, obtendrás una racha.", </del> <ins> "Un gif mostrándote como puedes pulsar en tu imagen de perfil en la esquina superior derecha conectar tu portafolio y GitHub.", "Dale un vistazo de tu portafolio de código. Pulsa en tu imagen en la esquina superior derecha. Para activar tu portafolio de código, necesitaras conectar tu cuenta de GitHub con Free Code Camp. Tu portafolio de código muestra tu progreso y cuantos Puntos Cafés tienes. Puedes obtener Puntos Cafés completando desafíos y ayudando a otros campistas en nuestras salas de chat. Si obtienes Puntos Cafés varios días consecutivos, obtendrás una racha.", </ins> "" ] ]

[X] Learn how Free Code Camp Works [X] Create a GitHub Account and Join our Chat Rooms [X] Configure your Code Portfolio [X] Join a Campsite in Your City [X] Learn What to Do If You Get Stuck


Question: (getUserInput) => $.get(getUserInput('url') + '/_api/get-tests?type=functional&n=4').then( (data) => { <del> assert.equal(data.assertions[3].method, 'browser.element'); </del> <ins> assert.equal(data.assertions[3].method, 'browser.elements'); </ins> assert.match(data.assertions[3].args[0], /('|")span#dates1/); assert.equal(data.assertions[3].args[1], 1); },

<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --At the affected page the following code snippet is given: But, according to the documentation of the function, the second argument is supposed to be a message and not the number of elements found. To check that an element exists n number of times, assert.elements() should be used. Affected page System (please complete the following information): Device: Laptop OS: Windows 10 Browser: Firefox Version: 86.0 Additional context Add any other context about the problem here.
Hello there, Thank you, for pointing this out. I can confirm this is incorrect. I am opening this up to first timers, and expect the best change to be: 1) Change the lesson to include () 2) Change the test to look for instead of (test is located in same file as lesson) An issue with the help wanted or first timers only 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


Question: var challengeSeed = !{JSON.stringify(challengeSeed)}; var challengeEntryPoint = !{JSON.stringify(challengeEntryPoint)}; var passedBonfireHash = !{JSON.stringify(bonfireHash)}; <ins> var bonfireName = !{JSON.stringify(name)}; var started = Math.floor(Date.now() / 1000); </ins> .col-xs-12.col-sm-12.col-md-8 #mainEditorPanel form.code

<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --In the challenge CSS Flexbox: Use the flex-wrap Property to Wrap a Row or Column, the value wrap-reverse is defined: wrap-reverse: "wraps items from right-to-left if they are in a row, or bottom-to-top if they are in a column." This definition is not correct. Actually wrap-reverse wrap content changing de cross-axis direction, bottom to top in a row, and left to right in a column. Browser Name: Browser Version: Operating System:
I'd like to take on this issue please
Since the curriculum content is in the repo, I submitted the PR there.
Ok, thanks Simon.


Question: # --description-- <del> In the Present Perfect Tense, y`for` and `since` are used to discuss time duration and starting points. </del> <ins> In the Present Perfect Tense, `for` and `since` are used to discuss time duration and starting points. </ins> `For` tells how long something has been happening. `Since` tells when something started. # --fillInTheBlank--

Describe the bug The first sentence of description contains rogue letter 'y', which needs to be removed: This is 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: Additional context 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.


Question:
<SearchBar innerRef={searchBarRef} />

  <Link id='universal-nav-logo' to='/'>   <Link id='universal-nav-logo' to='/learn'>  <NavLogo /> freeCodeCamp.org </Link>

Currently when clicking the freeCodeCamp logo in the navbar while on /learn it takes me to the landing page: Instead, clicking the logo on the navbar should take me to /learn. Aside from your first time arriving at / there is never a reason to be taken back there.
I made a PR here, although I'm not sold on the function. I agree that nobody will need to go back to the home page, but it seems a little unintuitive to have it go to when a home page exists.


Question: You should add the `flavor` class to your `p` element. ```js <del> assert(code.match(/<ps*class=('|")flavor1s*>/i)); </del> <ins> assert(code.match(/<ps*classs*=s*('|")flavor1s*>/i)); </ins> ``` You should only have one element with the `flavor` class.

This test is whitespace sensitive when it shouldn't be. Fails: Passes: Valid HTML should pass. No response All No response


Question: ); ``` <del> `insertionSort` should return an array that is unchanged except for order. </del> <ins> `insertionSort([1,4,2,8,345,123,43,32,5643,63,123,43,2,55,1,234,92])` should return an array that is unchanged except for order. </ins> ```js assert.sameMembers(

The following challenges have an example function call in the seed code. These function calls should be removed and the related tests should be clarified to reflect the call instead. This sorting challenge is correct and could be used for reference.
Hi, nhcarrigan. I'd like to try to help and solve it. I'm still learning about the project so I would like to ask a question so I can understand the issue better. There is a function call in the file.. bubleSort([1,2,3....]) (example: implement-bubble-) ! And it should be removed from the seed section and transferred to here, similarly to implement-quick-sort: ! ! Is it correct or are there other files that I should be concerned about?
That is correct, yes - this same change should be completed on the four files I've linked. I would, however, recommend holding off on working on this until we receive additional consensus that this is the best way to proceed. If you run in to any questions, feel free to review our or ask in our or the .
Sounds great!! Thanks for the fast response. I will wait until further notice.
Hi MuriloMarquesSantos, are you still interested in fixing this issue?


Question: 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]);

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!


Question: <del> --- title: Create a dummy file with a specific size --- ## How to create dummy files with a specific size using the "dd" command: The "dd" command can be used to create a file of a specific size. This is useful if you would like to test download speeds, or any other tests, and need a file of a specific size. ``` dd if=/dev/zero of=file_name.txt bs=1024k count=10 ``` This will create a file of 1MB called file_name.txt. bs is your byte size and count represent the number of blocks. An easy way to look at is 1024K X 10. Here is an even simpler way to create a 1MB file: ``` dd if=/dev/zero of=file_name.txt bs=1MB count=1 ``` </del>

<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The directory below is meant to say 'create-file-with-specific-size'. Specific is misspelled as 'sepcific'. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Browser Version: Operating System: If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
i am taking this issue


Question: Documentos: Actualizadas recomendaciones de contribución ``` <del> Se breve, no más de 50 caracteres. Puedes añadir información extra en la descripción del mensaje. </del> <ins> Sea breve, no más de 50 caracteres. Puedes añadir información extra en la descripción del mensaje. </ins> esto no supone ningún esfuerzo adicional respecto a mensajes como 'update file' o 'add index.md'

from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at  When you make a PR for this particular issue, do not tag it with instead just reference it with
Hey ! How could I claim so we don't double work? Thanks
Hi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.
I just open a PR for
thanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.
Done translating ! My PR is available at ! Thanks for all you do, freeCodeCamp
I have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Hello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-
Working on /docs/spanish/how-to-work-on-guide-
Hello, I've improved the file
Hello, Improving docs/spanish/how-to-catch-outgoing-emails-
Hi, I'm improving docs/spanish/how-to-work-on-coding-
Hi, can I help with /docs/spanish/how-to-setup-freecodecamp-
Sorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated
Hi! Is there any remaining documentation where I can help translate?
you can improve or fix redaction and spelling errors.
Hi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks
Where I can start helping?
sorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.

Hey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder
Hola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type "date" not type "fecha". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!
I agree that we should standardize around informal. I agree with you that we should look out for words like "fecha" that have been accidentally translated during our automated translation process.
Hi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating "array" as "arreglo"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, "arreglo" means "repair" (), and it makes any programming related text even harder to understand.

This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that "arreglo" was the (really bad) translation of "array". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is "ristra". According to the : Which basically means: "A group of things placed one after another" They also share all the phonems in "array", with the adittion of /r/ (rolling r) and /t/ in "ristra". I'm open to other candidates, but please, let's take "arreglo" out of the Spanish version. The word "array" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like "list", "function", "import", "scope", etc. [1]: [2]:
Hello guy, I vote for yes, let’s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190
Thanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations.

We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.


Question: ] ], "type": "hike", <del> "challengeType": 6 </del> <ins> "challengeType": 6, "nameEs": "Herramientas de desarrollo de Chrome: red", "descriptionEs": [ "La pestaña network (red) ayuda a responder preguntas como '¿Qué elemento o parte de la página fue el más demorado?' o '¿Qué inició una petición?'", "El panel de red registra información detallada sobre cuánto tarda en cargar cada elemento de su página o aplicación.", "Cada solicitud se registra en la bitácora, que se puede encontrar en la parte inferior del panel de red.", "Si te fijas en la línea al lado derecho, te darás cuenta de un patrón de colores. Cada color representa un tipo diferente de contenido en la solicitud. ", "Cuanto más larga sea la línea de un color determinado, tanto más tiempo tomó ese tipo de contenido en la solicitud. En últimas quieres líneas cortas, y si cualquier solicitud tiene largas líneas, sabes que puede estar ralentizando la página web.", "Si pulsas sobre una solicitud en la bitácora, podrás obtener información más detallada.", "Consulta más documentación detallada aquí: developers.google.com/web/tools/profile-performance/network-performance/resource-loading" ] </ins> }, { "id": "56b15f15632298c12f315182",

[x] Chrome Dev Tools: Elements [x] Chrome Dev Tools: Network [x] Chrome Dev Tools: Sources [x] Chrome Dev Tools: Timeline [x] Chrome Dev Tools: Profiles [x] Chrome Dev Tools: Resources [x] Chrome Dev Tools: Audits [x] Chrome Dev Tools: Console [x] Chrome Dev Tools: Summary
Working on it


Question: ```js <del> assert.match(code, /authorContainer.innerHTMLs*=s*(`|"|')<p.*>.*</p>1/) </del> <ins> assert.match(code, /authorContainer.innerHTMLs*=s*(`|"|')s*<p.*>.*</p>s*1/) </ins> ``` Your `p` element should have the class `error-msg`. ```js <del> assert.match(code, /(`|"|')<ps+classs*=s*("|')error-msg2>/) </del> <ins> assert.match(code, /(`|"|')s*<ps+classs*=s*("|')error-msg2>/) </ins> ``` Your `p` element should have the text `There was an error loading the authors`. ```js <del> assert.match(code, /(`|"|')<ps+classs*=s*("|')error-msg2>Theres+wass+ans+errors+loadings+thes+authors</p>1s*;?/) </del> <ins> assert.match(code, /(`|"|')<ps+classs*=s*("|')error-msg2>Theres+wass+ans+errors+loadings+thes+authors</p>s*1s*;?/) </ins> ```

The code provided below does not pass, even though it should. The test does not allow for an optional whitespace between the backticks/single or double quotation marks and the element - in this case a paragraph element. The hint message does not suggest that campers keep the code in one line. In fact, throughout all the curricula, I've been under the impression that creating several lines for setting improves readability, and is, therefore, good practice. So, I don't see any reasons why the tests shouldn't allow this formatting. Since I was not sure whether my code generates an essential difference on the UI/Webpage, I tested it. There was no difference. So, I thought this might be a bug in testing. I filed a PR on this issue. I am quite new to contributing and still learning. Please let me know if there is anything I've done that did not follow good practice. The test does not allow for an optional whitespace between the backticks and the element. It should. ! Device: Laptop OS: Windows 11 Browser: FireFox Version: 125.0.2 (64-bit) No response