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

React JS, SASS, Javascript State Variables Into Inline CSS

Chris Paschall•440
@ChrisP1108
A solution to the Pomodoro app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Everything seems to work as I planned. There wasn't any information as far as if the clock should count down or count up from 0, nor if the circular progress bar should start full and go backwards or start at nothing and go to full.

I set it up so the clock counts down and the circular progress bar starts at nothing and goes to full once the clock has counted down to 0.

I utilized a bit of inline CSS styling with Javascript state variables to make the colors, fonts, and circular progress bar change accordingly. I also utilized setInterval to call a function with if/else if statements to evaluate conditions and change the clock accordingly, along with calculating the total number of minutes/seconds remaining by the value remaining on the progress bar to increment the circular progress bar accordingly.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • hardy•3,640
    @hardy333
    Posted almost 4 years ago

    Hey, very nice solution, good job, as you sad everything works just fine.

    Animations are very cool.

    Few thing you can fix:

    • On firefox number inputs still shows default up and down arrows on number inputs to fix that use this: input[type=number] { -moz-appearance:textfield; } .
    • On both chrome and firefox number inputs has bugs while trying to set inputs by keyboard instead of clicking up/down arrow keys, I don't know what the bug is or why it is happening, so basically if you type 1 or 0 on inputs then thy lock on that value and user cant change by keyboard, but it is working if you click up/down arrows.

    Few additional features you can add if you want:

    • localStorage support in order to maintain settings state such es font-family and color even if user refreshes browser.

    • very small thing but very important in my opinion: numbers on circular pomodoro clock are constantly changing their sizes since every second there is different number on screen. so try to gave some fixed width value to number container in order to fix shifting and moving other numbers... hope you will understand what I mean.

    Good luck.

    Marked as helpful
  • hardy•3,640
    @hardy333
    Posted almost 4 years ago

    Yup it works... good job...

    Marked as helpful

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