Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

React app with Flexbox and SCSS

Michael Bishop•1,080
@MikeBish13
A solution to the Memory game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • htmlHxcker•70
    @htmlHxcker
    Posted almost 4 years ago

    Hi, Awesome work on this challenge, I understand that it's a bit complex and so you did a lot with this so good job on that. I did notice a few bugs though, which while they don't break the functionality of the app could make the usability of the app a smoother experience. Here are the things I noticed.

    1. On Devices with a width less than 320px (Mobile S in Chrome DevTools) the blue background doesn't take up 100% of the screen and instead gets cut off towards the bottom, this also happens when results are displayed.
    2. Sometimes, if I double click on a covered tile, it automatically opens up the solution (To be honest I didn't want to tell you about this one just because it seemed like a fun way to hack the game LOL)
    3. Speaking of Tiles; If I clicked too fast I found that I could get 3 tiles to be opened all at once, inversely, sometimes if I click too fast it closes other tiles and opens just one tile(The last tile I clicked).
    4. You did a good job! Now I have to give a disclaimer, I didn't go through your code because I am also working on this challenge (I in fact had to use my mentor points to view your solution out of curiosity) and didn't want to cheat but from what I can see as an end-user, this is very polished and well done, the points above are things you could work on if you feel like since they don't necessarily break the solution, Hopefully, if I complete my solution then I can look through your code and maybe you could look through mine too, Cheers!.
    Marked as helpful
  • Matt Studdert•13,611
    @mattstuddert
    Posted over 3 years ago

    You've done a brilliant job on this challenge, Michael! It's great to hear you enjoyed working through it. I've just spent a good 10 minutes playing, so you've done a superb job making the game flow nicely!

    My main recommendation would be to add some focus states to the buttons to allow for keyboard navigation. There aren't any focus states at the moment, so it's not possible to tell which button element has focus.

    Keep up the excellent work! 👍

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
Frontend Mentor logo

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.

Oops! 😬

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

Log in with GitHub

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub