Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 28 days ago

Time tracking dashboard

fetch
yekta_akhavan•170
@yektaakhavan
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

"How to style the three-dot icon image so that when the mouse hovers over it, it becomes white and the cursor changes to pointer? Is it possible to do such things for an image?"

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Allan Abok•580
    @abok-cymk
    Posted 28 days ago

    1. Changing opacity on hover

    .ellipsis:is(:hover, :focus) {
    opacity: 0.5;
    }
    

    2. Should you use it?

    Yes, but here are important things to consider.

    Pros

    • Simple and fast way to create a hover effect.

    • Doesn’t need extra elements or JavaScript.

    • Good for indicating interactivity (e.g., image is clickable).

    Cons

    • Makes the entire image and its content transparent — even if it contains overlaid text or other elements.

    • Affects child elements' visibility, which can be a problem if your image contains other layered elements (like icons or text).

    • May not be accessible — low contrast might confuse users with visual impairments.

    Alternatives you might prefer

    • Instead of reducing the image's opacity, sometimes it's better to overlay a semi-transparent layer or use filters:

    Option: Use filter

    img:hover {
      filter: brightness(50%);
    }
    
    • Keeps the image visible but darkens it.

    • Can be combined with transitions for smooth effect.

    Marked as helpful
  • Dusvy_M•520
    @dovelm
    Posted 28 days ago

    very good job

  • Allan Abok•580
    @abok-cymk
    Posted 28 days ago

    You have a typo on your icon names

    E.g "/icon-Social.svg" instead of "/icon-social.svg"

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

Oops! 😬

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

Log in with GitHub