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

time tracker dashboard

James.•460
@Jimztech
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

Working with json file, was the main challenge I faced. The second challenge I faced was the overlapping of the boxes, I had to learn z-index and really understand positioning in css.

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

How to get the element active with a color of white when clicked.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sajana Wijesinghe•460
    @StormKing969
    Posted 8 months ago

    The reason why the text won't turn white when clicked is because of the opacity that the 'daily-list' has. It basically darkens the color you placed on the timeframes. The easiest fix I can think of is adding the opacity based on what's selected and not selected. Also, I did create a pull request on your Github page if you want to see the solution.

    Marked as helpful
  • Michael Balogun•240
    @Emynex4real
    Posted 8 months ago

    A very easy way of toggling the daily list white is using an if statement

    weekly.style.color = 'white' if(weekly.style.color = 'white'){ daily.style.color = '#ffffff7f' monthly.style.color = '#ffffff7f' }

    but you will use an else if to flip incase another is clicked Ihope you understand what i am saying

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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