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

Comments Challenge completed via React

P
Justin Green•2,940
@jgreen721
A solution to the Interactive comments section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


React Comments

Featuring

  • JS confetti library to celebrate a LIKE 👍 🙌

  • Ability to update a comment 💬

  • Parsing function to detect some tech language terms and generate a link. Use a hash to make sure there's no duplicates.

-Input Character counter to (try!) to limit your banter!

Feedback and suggestions welcomed! 🙂

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nick C.•690
    @niemal
    Posted about 2 years ago

    Hello there,

    This looks pretty solid congratulations! I have a suggestion to make, at least on the mobile version:

    When you click on an upvote button, the button hover-states and remains hovered. You might want to do something about that and remove the hover on mobile or just make it a keyframes animation on mobile.

    Last but not least fixing the accessibility report on this page should also be a fine task to take on.

    Overall solid, love it, keep it up!!!

    Marked as helpful
  • P
    Justin Green•2,940
    @jgreen721
    Posted about 2 years ago

    Appreciate the feedback and bug finds! Yea I need to always be a bit better on the accessibility portion and think I will clean it up.

    I initially did some 'reaction' restraint logic but took it off figuring why not allow a few more clicks but yea, I just put a global counter in there that will kick in after 8 clicks. As far as persistence I did think about attaching a firebase or something and may end up doing that. I realize there are other manners but ya, I just didn't go the persistence route at this point. It's definitely a good template exercise for it though!

    I did tidy up the bug with a @media and @keyframes adjustment. The animation can sometimes look a little funny but not bad. I then added a boolean so when you can't click anymore all hover-events will/should?? be stripped. lol

    Again appreciate the replies! 🙂

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

Oops! 😬

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

Log in with GitHub