Linting fails on local environment in some cases. Issue did not reproduce on GitPod. update-email to the root directory Execution fails with the message under Linting should be successful No response Device: Macbook Air M2 OS: MacOSThis issue was originally raised in Discord: Thread created with the full error log: A contributor also ran into this issue in the past: Note that the lint operation in this one ran against the entire project () rather than a single file.
Thanks for opening this issue. I'm not able to reproduce the issue locally, so I'll need your help with this: Add: after this line: Commit this change using the flag Make a change to and check if you can commit the change without the flag This is to check if those rules are the culprit as I did run into some performance issues with them in the past. Here is our eslint current performance, in case anyone is interested: <img width="521" alt="Screenshot 2023-12-18 at 13 58 26" src=""
Thanks for your help I am still facing the issue. I the two lines after line 89, committed with --no-verify. I a space to and tried to commit without the flag. Attached the stack trace.
It seems like the memory allocation on your machine is capped at 2 GB. I tried reducing the limit to 512 MB using the following command, but could not reproduce the issue still: I'm wondering if it works if you increase the value on your end to . So please try this: In the root, add the following line to the "scripts" block: Then run in the terminal
Fixed it! I tried running but that did not seem to update the memory allocation when I ran Instead, I ran something similar to your command in the terminal - This fixed it. Thanks a lot! Should we add this in the documentation?


I think we can make the instructions more clear. They are a bit confusing. Or something like that. Clear instructions. 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:
I think that is much clearer. We can open this up for contribution
Hi, is someone working on this issue? If not, I'd like to contribute.
We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.


In Step 59 of the Music Player project, the following code is valid as JavaScript code, but our test doesn't accept it. Notice that and are wrapped with different quotes. or The test is here: Reported in these forum posts: If we want to allow the mixing of single and double quotes, we should fix the test. If not, we should add a hint to guide users to use either single or double quotes. ! 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
Yeah, I agree that campers should be able to pass with either types of quotes because technically they did get the question right. I have opened this up for contribution


In "Playwright-Gitpod Setup" section of "How to add Playwright" tests page, it's missing the step: cd to e2e directory, readers can be confusing and run the command in the root directory, this will cause error to "How to add Playwright tests" page, "Playwright-Gitpod Setup" section: step 3, you can see the missing step: cd to e2e directory (this step is in section) Update the doc to add the missing step !
An issue with the label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors. If you would like to contribute, and have not read the contributors docs, please do so here: If you have any issues with contributing, be sure to join us on the , or on the To close this, add within the same codeblock as the text. The file to change is located within the directory. Only the English file should be changed.
updated the documentation part of playwright tests
If you've made a fix, you can Let us know if you need any help.
I'm new to contributing and I really don't know a thing about how to do it or its working Please help me in my learning
You can read this guide:


Instructions text says "findIndex is an array method that lets find the index of the first element in an array that satisfies a given testing function." Following the style of previous similar statements in the course, "lets find" should probably say "lets you find". "lets you find" instead of "lets find" No response Device: laptop OS: Windows 11 Browser: Chrome Version: 120 No response
Hey ! That's a good catch. But after reading through the directions there are a few things that could be cleaned up to simplify it a bit and there are a few things missing like the markers to indicate a new term is being introduced. Let's go with this revised description js const numbers = [3, 1, 5, 6]; const firstNumLargerThanThree = numbers.findIndex((num) =num 3); (firstNumLargerThanThree); // prints index 2 ` I'll go ahead and open this up for contribution.


The answer is wrong for this page. N/A I expected the correct answer to be 'They focus on presenting information rather than programming logic.' But the correct answer appears to be 'They lack the ability to create webpages.'. <img width="845" alt="image" src=""I think the system is irrelevant, so I am skipping this. No response


This step comes up a lot on the forum and I think it is because we have never really explained what method chaining is or showed an example. Let's update the description to include an example so they know what to do. We should also explain why the join method is needed here so they better understand what is going on. js const exampleArr = ["This", "is", "a", "sentence"]; const sentence = (" "); // Separator takes a space character (sentence); // Output: "This is a sentence" js ().join(); ` 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


None of the GET request examples/Tests mention to be able to GET with id param, However during one of the PUT request tests there is a GET request sent with an ID, i struggled to find this Bug in my code, i feel adding one extra Functional test for GET request specifically requiring to be able to GET by IDs, If using mongoDB like i was the ID needs the toString Method in order to be read as a string. i attached a screen shot shows the PUT test with the GET request at the bottom Either extra functional test requiring to be able to GET with an ID, or Updated with GET example that shows GET with an ID ! Device: [Desktop] OS: [Windows 11 WSL Ubuntu 22.04.3 LTS] Browser: [Chrome] Version: [122.0.6261.70 ] No response_
This requirement would be covered by: I'd be fine adding another check inside that existing test to look at the param.
i see now the "any field" and value, this was a lack of knowledge at the time, being able to get data by an "id" is imperative. Id like to propose a solution to the test above, change query of to GET the post created by carol and assigned to eric, this keeps the get Multiple aspect but returns 1 doc the of to GET and assert that of is equal to of
I'm hesitant to rewrite the entire tests, when instead we could update the test I indicated to try a query by ID (which we know won't break existing projects because a later test relies on that functionality).
Agreed my proposed solution would be for the existing GET test that you indicated, you could just drop in and after existing , this adds a query by ID. The current tests only query by and !
Ah, I see. Yes, that would be a good approach. I'll go ahead and open this one up.


On Settings page, the empty space between the "Certifications" and "Legacy Certifications" seems to be missing. <img width="840" alt="Screenshot 2024-03-12 at 12 04 47" src=""We could add a to space them out a little. The Spacer should go in between line 421 and 422.


The instructions say, in part: A literal (heh) reading of these instructions resulted in a learner producing this code: I read the instructions and could not figure out what the template string was supposed to do. I had to check the next step. I'm still confused, because a join produces a string output, so it seems completely superfluous. See above. I don't know exactly how to reword this, but the "all of those" is probably too ambiguous. No response N/A No response
Yeah, I agree. it is not clear what it is pointing to. It could be reworded as, Or something along those lines. The next steps is adding a hyphen followed by So the final result will be this
May I proceed to create a pull request to address this issue? I require a merged pull request contribution for my university assignment in open source.
This wording looks good to me. If you want to create a PR you're welcome to do so.
I am currently addressing this issue and have submitted a pull request.I would greatly appreciate it if you could review my pull request at your earliest convenience. If the changes meet the project's standards and requirements, I kindly ask for your assistance in merging them.This contribution is essential for my university assignment.


The instructions state: And will only check as the right answer if you place these 3 values in that specific order. This answer should be correct regardless of the order of the values. 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


it is confusing whether campers will pass string of 'Players' or variable named . i think the wording should be cleared on the hint. ! Your parameter should have a default value pointing towards the variable named . something like this should be on the hint ? ! OS: [Windows 11] Browser: [Chrome] No response
I think it would be best to update the description to remind campers where came from some thing like


To make it clearer what the syntax should be for accessing the last element of an array, let's go with this updated description js array[ - 1] ` 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


We are getting a lot of confusion on the forum about step 18. The confusion stems from not know how to log the array to the console. So we should update the code example in the description to log the example array. That should help with what is expected to do. js let array = [1, 2, 3]; array[1] = 25; (array); // prints [1, 25, 3] ` 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


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


Opening for visibility. I have not seen this happen myself, but I also haven't spent much time in the editor. Link to threads reporting this. Unknown, I guess usage over time. Performance not degrading over time. 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
I've experienced this issue multiple times. After the donation pop-up appears, the performance of the website becomes laggy. Even after refreshing the page, it returns to normal temporarily, but the lag returns once the donation pop-up reappears. ! Note: the lag doesn't occur immediately after the pop-up, it becomes noticeable as you continue solving challenges, with delays in typing and overall slowness.
I have not noticed this in the dev environment, even if the pop-up is present there too (python course)
I thought I was crazy or that my machine was "too old" for this, but I have experienced this too. In my experience, it has happened after working a while on the editor or just doing a little bit of work on the editor, leaving it open, and then coming back. It becomes really slow and the only workaround that I have found is closing my browser completely and opening it again. Note: As a current donor, the pop-up doesn't show up in my account and I don't think is related to that component itself.
Commenting to add I experience this every single time I use the editor for more than maybe 20 minutes. It doesn't just happen suddenly. It starts with a slight delay then gets worse and worse. I just opened up Incognito with no extensions enabled, and I noticed the delay after around 15 minutes. Then by 25 minutes it was definitely worse. It isn't unusable, but if you type relatively quickly it is very noticeable that words on screen are being completed maybe 100ms after you actually type them, then gets a little worse from there. Info: Chrome/124.0.6367.158 (no extensions) macOS Ventura Responsive Web Design Certification (I have had delays throughout this entire course)
I'm able to get the slowdown both in production and in development. Reproducing it a bit loosely: Go through multiple steps (around 20?). At some point writing few characters in a row will start feel delayed/lagged. In console start appearing warnings, something like [Violation] 'input' handler took 1123ms. Recorded performance showed then longer times of redux updates coming from (if I didn't mix up anything) the editor's :
Thanks, that's really helpful! Just so I'm on the same page: how did you record the performance and did you have campfire mode on while you were testing this? Also, did you complete and submit 20 steps or just navigate through them?
Hey It was the Performance tab in the browser's developer tools. Not the profiler from react developer tools. Once I noticed the lagging, I turned on recording and did couple more steps. Then stopped recording, and tried to make heads or tails out of it :eyes: It doesn't seem to be related to campfire mode. I actually have campfire mode on in production, but when I was checking in development I believe it was off. Steps were completed/submitted. I haven't tried just navigating them.
It's not easy to read, but it does seem to be that's taking the time, which makes sense. That's what I see even when the editor is working normally. I've yet to see the slowdown from having the editor open for a long time typing a lot in a single page navigating through 80+ challenges I'll try completing a lot of challenges next and see if I see what you saw, Regardless, it seems like either the amount of typing you need to do to complete a bunch of challenges OR the completion/submission process is the problem. That's my current guess.
I'm seeing the same code editor latency after about 5 to 10 minutes of usage. I see it both in Chrome and Firefox browsers when testing in Windows 11 and Linux Fedora 40. The best solution I have is to do a of the page when it starts happening. Is the code editor overloading the cache to cause a slow down?
I'm on Windows Chrome browser and the editor is super slow for me. I type and I can't see what I've typed in till seconds later (good thing I'm a good typist) and I click Submit and it takes a long pause to respond. I tried clearing cache but it fixes the issue for maybe a couple of steps max then back to the slow performance. Definitely something I didn't experience back in early 2023 when I last used the curriculum. If there's some data I can collect to help debug, let me know. (Edit: i switched to MS Edge which I didn't use for fcc work before and the issue disappeared for the first 10 steps i tried). I may continue here for a bit before retrying chrome again at some point.) 2nd Edit: the performance improvement didn't last. Same issue occurred after a few more steps and I persisted for a couple more of these slow steps just to see if anything would change, but nothing did. So I logged off and switched back to Chrome. First few steps are back to normal performance at this point. Perhaps the pattern will repeat (and things will slow down momentarily at which point I will try another browser switch).
Hi all, thank you for reporting the issue. We are trying to reproduce the issue, but no luck yet. From what I gather, the issue can happen: On any OS (so far we have reports on MacOS, Windows, and Linux) On any browser (so far we have reports on Chrome, Firefox, and MS Edge) In both incognito and normal browsing modes With or without browser extensions To both donor and non-donor users With both campfire mode enabled and disabled I guess what's left is the challenge pages that you are on when you experience the issue. I personally have tried going through 50+ Python challenges of the , and I haven't experienced the lag. We have one user experienced the issue with the Responsive Web Design challenges (), so maybe this is where I'd try next. But we would love to get more information from everyone else: which page / course you were on when you experienced the issue. Thanks again for reporting.
The lag happens consistently to me on the Role Playing Game project (js beta) pages. Everytime I recycle my browser the issue goes away temporarily. (Or if I close the tab on edge and reopen it)
As I have , I experienced this throughout the responsive web design cert, but I have since finished that course and moved onto the JavaScript one, and can confirm I am having the exact same issue on there. The easiest way I've found to get rid of the delay is to reload page while ignoring cache.
It might be needed for user to be logged in. I've tried to reproduce it on Firefox. I've went from last steps of to about 30 step of the - without being logged in, no issues. Then after logging in, I started at the first step of , passing code was still in browser, so was just submitting it for the most part. By the 20th step writing was again slowing down. Edit: although Firefox doesn't display warning in console.
I also see it when logged in. It literally became so bad that is spiked the CPU if I held down a key and just let it repeat. It might somehow be related to the completion modal in the lower jaw, but I'm really not certain. That is at least also different depending on if you are signed in or not. The problem is, it didn't seem as bad in dev mode for me, so I'm not confident. But I removed the progress component and did twice as many steps, and it didn't happen. But as said, I'm really not sure if I trust it in dev mode. In the Performance log, looking at the bottom-up tab, was the first one.
Thanks everyone. I've finally reproduced it by doing ~20 responsive web design lessons while signed in. It does seem like is part of the problem, thanks I'm not sure it's the root of the problem, but it's definitely getting called far too often. My plan is to create a quick PR to stop the unnecessary calls and/or memoize the function. Hopefully that fixes it, but we'll have to see.
I was briefly looking at the Progress component and saw ProgressInner  Something about that code doesn't sit right with me. The and variable names seems a little like something that wasn't fully checked and tested. If I just log when the component renders, it does so on every keystroke, and even just left-clicking inside the active editor section logs a re-render. This is after you have completed at least one challenge step. ! Might not be related, but it doesn't seem right considering it isn't even shown. I'm a little skeptical of the Intersection observer and useEffect. I know this isn't very constructive, but that's all I've got for now.
I agree about the naming, it's a little sloppy. And, yes, something is going wrong meaning that it's getting re-rendered after challenge completion. makes it a lot better, though. It's still rendering when you start a new challenge (and it shouldn't), but it no longer renders in response to, well, everything.
I have unpinned the issue, considering it is closed as completed.
Hi Guys i am still experiencing this on two separate machines both running windows 11 and Chrome Browser extension installed , ublock origin and Ghostery this is whilst going through the responsive web design curriculum, in both building a balance sheet and the cat painting projects. I have experienced this behaviour both before and after i became a supported, and most recently experienced it about 5mins ago
Thank you for mentioning. However, the potential fix for this has not been deployed to production yet. So, until that is deployed, you can expect the issue to be present.
Hi everyone, the potential fix has been deployed, please report back if you're still experiencing the issue. Thank you for your patience, and happy coding.
hi , I've been using the JS beta curriculum all day from a single tab today. I did end up running into the performance issue again but it took a -lot- longer to run into it, and it was not lagging as bad as it used to when I would type (one of the issues I saw was that I would type and it would take a bit of time for the editor to display what I typed). Now when it slows down, the lag is not nearly as long (and as I said, I ran through a lot of steps today before seeing the slow-down). This is just to let you know what I have observed as you've asked us to report back. Thanks for the fix(es) already done.
Thanks for the follow-up, Some slowdown is expected, since the 'fix' was to make rendering considerably more efficient. This delays and mitigates the slowdown, but clearly something is getting less efficient over time. Since it's not too bad at the moment and it's hard to pin down the ultimate cause, I think we can leave this for now. We do plan to give the client some love before too long and that will give us another chance to squash the bug.
Hi Guys I am still running in to this issue, im currently working my way through learn-basic-javascript-by-building-a-role-playing-game. and after about 10 mins the typing of text starts to lag, im having to refresh the page and it seems to make it go away for a while
Other reports of slow performance
Thanks I'll give this another look.
should be another decent perf boost. Same deal as last time: while I expect this to be a lot better, there may still be deeper problems.
Tentatively closing again, since has been merged and should help considerably.


in step 20 of the JS building a pyramid generator project, the step refers to the " rows[2] assignment" but should instead refer to the "rows[ - 1]" assignment as that is the line in the code at that moment (not the "rows[2]" line. As the step begins with the code as given above, the instructions shouldn't say "rows[2]" to refer to the line "rows[ - 1]" (therefore a small correction to the correct line of code is needed) ! Device: laptop OS: windows Browser: chrome Version: No response
Second test also will need to be changed accordingly.


Lesson asks you to, "declare a regex variable. Assign it a regular expression that matches a number (including decimal numbers) followed by a or / operator followed by another number," but will accept regex' from users that don't satisfy this criteria (examples /d/ and /5/, matching anything with just a number, and anything with a 5 in it). Related issue to address test being too strict. Opened from forum post: Lesson should pass when Regex matches against a number, followed by a or / operator, followed by another number, but matches any number. Regex's that pass but should not (likely not limited to): /5/ /d/ // 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
It looks like the last test to could be updated to include a few more assertions like this js assert.isTrue(highPrecedence("53")); assert.isFalse(highPrecedence("5")); assert.isTrue(highPrecedence("10/2")); assert.isFalse(highPrecedence("")); But also, looking at this challenge again, I think it could be simplified. At this point, we should only be testing for the final result and allow campers to solve it however they want to. Here is my proposed update js assert.isBoolean(highPrecedence("122")); js assert.isTrue(highPrecedence("53")); assert.isFalse(highPrecedence("5")); assert.isTrue(highPrecedence("10/2")); assert.isFalse(highPrecedence("")); I'll open this up for discussion so the other members can chime in with thoughts.
I see this as the only test for the regular expression itself: Your variable should be a regular expression. does this issue require the addition of more tests? and if so, should there be seperate tests for each regex that produces an unexpected behavior like /5/ and /d/ or just one test that ensures the regex conforms to what was asked for (includes the two numbers, * symbol, / symbol, and 3 capture groups)?
The test you mentioned here only checks that the a regex variable was created and that some sort of regex is being used Currently this test is checking for the correct result js assert.strictEqual(highPrecedence("53"), true); but it right now allows for multiple incorrect answers My proposal is to rewrite the lesson to allow for more correct answers and ensure that incorrect answers don't pass. Right now, you have to create a regex variable and you have to return But there are dozens of correct answers and this should be rewritten to allow for that. So you can see my note here for my proposed changes The thing we want to be carefully about is not using regex tests to check for this. Because that is what is happening for the other lessons and it is difficult to maintain and only allows for a specific answer. So that is why this is marked as open for discussion
Opening this up for contribution - a PR which resolves this will follow Jessica's updated approach in to test the function result, regardless of the function implementation.


The following classes in are unused and should be removed: .help-modal .help-modal-heading .btn-lgRemove the above classes from Test and confirm that the modal displays properly after the changes


Timeout limits are too aggressive on this problem and blocking users from computing the correct answer. Verified via , the code above produces the correct number of semiprimes for 1, 10, ..., . However, for , we have a timeout. This code could probably be a bit more efficient, but even if I just cut it down to finding all primes < , it times out, indicating that it is not possible for campers to complete this exercise with the current infinite loop protections on this problem. All?
Seems like a good challenge to just remove the loop protect from entirely.
Seems like a reasonable fix to me


On step 89 and 90 of the Pyramid generator there is this misterious error that appear, it can be confusing for campers. !
Error is coming from the function, specifically one of the string repeats. Depending on the and , when or will be , calling method of string will show that error. Edit: When condition is there's no such issue.
Yep. I think reworking the lessons so we never leave the learner with broken code (or at least never unexplained broken code) is the way to go.
I'm not sure if it was even intended to have broken code, description is suggesting everything should work fine. Step 91 asks for two changes, one of which specifically makes this error appear (second change fixes the issue).
Yeah, it's a bit confusing. Probably not intentional, though. On 91 there's this: the only time I don't see the error is when I've followed all the instructions on step 91.
Is this not enough to clear up any doubts? Cuz after following the instructions in step 91, there's nothing mysterious about the error anymore.
I don't think so. Step 89, where error is introduced, doesn't mention it. Neither does 90. It's only when you reach 91 that the error is mentioned and the text is which is incorrect. Changing to has no effect on the error. It's only the combination of that and adjusting the conditional that finally removes the error. The main issue with this is that it breaks the feedback loop between learner's actions and the code's behaviour. Speaking for myself, everything gets harder when the results of my actions are essentially invisible. I know we run tests to check you re doing it right, but that's not really a substitute for them seeing how your actions impact the program.
Okay. We need to at least note the possibility of an unexpected error to the camper. I'm thinking on step 89 now.
Just for posterity, the steps got shifted. Error is introduced by completing step 95 Error is resolved by completing step 96 What should be changed here: Step 95 should: Introduce and explain the error Ask the campers to change the comparison to Step 96 should: No longer ask campers to change the to Not mention that creates a


I encountered an issue while completing a task (Step 11) on freeCodeCamp. The test involves using the method to determine whether a task already exists in an array and then either updating it or adding a new task. The problem appears to be related to the comparison order in the arrow function passed to . When I change the comparison order, the code works without any issues: ! ! and 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
You didn't mention the error caused.


When the blanks in a fill in a blank challenge overlap vertically, the top selection box gets cut off: <img width="767" alt="Screenshot 2024-06-17 at 5 39 59 PM" src=""^ See the two blanks in the sentence are above and below one another. When you click the first blank, the blue selection box is cut off - presumably because the input below is in front of the first input. to on the first blank in the sentence the blank get cut off The box to be visible We could adjust the spacing so the input doesn't get cut off, or move the z-index of the input to the front when it's selected.
I think changing the z-index on select makes sense.
We might also consider increasing the . The lines are pretty close together. Not sure why we are using for the unit, usually is set using unitless values, which would make the we have on the elements work much better. Also, the font-size is set using for whatever reason (unlike most if not all other font styles I have seen in our CSS). Not that changing it to does anything (currently at least).


Thanks for opening this issue. This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
I have fixed in my PR


I followed Step 4 instructions. As I finished typing out the element, by habit I press + , and noticed that it accepted it, even though it shouldn't have as I was still missing the element It should have failed, as it's still missing the that Step 4 asked for ! Device: PC OS: Window 11 Version 23H2 Browser: Firefox 127.0.2 (64-bit) No response
This seem to also happen in other parts of the same course, such as Step 7 ! As you can see, it is missing its closing tag As well as Step 11 ! It's missing its closing tag yet the Step still validate it
Can you please open a new issue for the form element. I'm guessing the browser is auto closing it, and we don't have a regex test for it. It should result in a valid form element, because the browser will close it. However, the element technically does not have any "Tag omission" so it should have an end tag in the HTML (even if it gets to the DOM by the browser).
Done


The keyword should be wrapped in a pair of backticks.
This issue is open to first-time code contributors to this repository. The file that you should be updating is: We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. 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. Happy contributing.
Hi! I'm a first timer and would love to contribute to this project and fix this typo. :)
Hey We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Issues labelled with or are open for contributions. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.
can i work on this issue if it still open


in step 98 of the platformer game, there are a couple of small issues that can be fixed. 1- the check is too strict for spaces because it doesn't accept this code: Note the extra space between the word draw and the parenthesis. Without the extra space, the code is accepted. For the second issue, the wording used in the step "add a fillStyle property to the ctx object" is not what I would expect given that fillStyle is a property of the canvas object and not something we 'add' to it. I would suggest a rewrite to "set the fillStyle property of the ctx object" instead. As seen above. slight wording change needed and a looser check to allow a space between the word draw and the parenthesis. No response N/A No response


"an checkbox input" should be changed to "a checkbox input". Fix the typo in the following files:
This issue is open for contribution. The file that you should be updating is linked in the original post. We typically do not assign issues. Instead, we accept the most quality contribution followed by the one that is made first. 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. Happy contributing.