Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 2 months ago

tic-tac-toe-game

jquery
P
Joel Eguiza•380
@joeleg96
A solution to the Tic Tac Toe game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

To be honest, I am very proud of every part of my solution. This has been the most fun and challenging project I have taken on so far. The HTML and CSS was very easy, but the JS proved to be tricky because of the asynchronous aspect of JS. I enjoyed the process of this project - every struggle and solution - so I wouldn't change anything.

What challenges did you encounter, and how did you overcome them?

One of the earliest problems that I came across was that when I would play against the CPU, the CPU would take more than 1 turn at a time. I eventually solved this by restructuring my JS; mostly just moving some things around.

Another issue that I encountered was being able to select a tile that had already been selected before, but I solved this pretty easily by using an array that initially contained all the tiles, and the corresponding tile space would be removed once it was clicked on, and then using an if statement within my functions to ensure that the space existed within my available tiles array.

One of the biggest problems I had though, was during PVP games. The asynchronous aspect of JS would trigger both player turns since they both relied on an event listener when a tile was clicked. I had to look up a possible solution, and found a switchTurn function, and adapted it to my code so that it would work with what I already had previously.

What specific areas of your project would you like help with?

The one problem that I wasn't able to solve was that the CPU would always take one final turn even after the game was over. I tried to implement a solution to this by using an if statement that would check if the "victory-container" was being displayed, and if it was it wouldn't allow the CPU to make another move, but it didn't end up working, so I'm unsure on how to solve that part.

Other than that, I would appreciate any feedback on possible improvements I could make, or if there are any bugs that I may have missed during my very long debugging process.

Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Joel Eguiza's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.