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

Expenses chart component

Piotr•250
@Piotrek1994
A solution to the Expenses chart component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Does somebody know how to write JS when I have mouse over each diagram, diagram is active and when I get mouse out of diagram, diagram goes inactive?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Isaac C Anyim•210
    @CreatorLZ
    Posted almost 3 years ago

    It's simplest if you were using react. You just need to set the hover effect and style it however you wish. I just completed this challenge. You can check out the code. For the black boxes on each bar, I set the initial opacity to 0 then targeted the components containing the boxes with an hover effect and set the opacity back to 1. This is possible as I used styled components. I must sound strange. Checkout my code. It's all there

    Marked as helpful
  • Md Raihan Alam•520
    @Md-Raihan-Alam
    Posted almost 3 years ago

    Hello Piotr, Congratulation on completing this project. I am going to answer some of your questions first. First, for the mouse hover in the js case, you can use 'mouseenter', 'mouseleave', 'mouseover' events. You can read this document for more details about the many mouse events and how to use them ->https://www.w3schools.com/jsref/obj_mouseevent.asp. Second, your site needs to be developed in the responsive case as I see It is not much of responsive yet but still ok for how far you have come. Try to make sure your site is responsive at least 320px as this is the lowest width of mobile now in current days so try to work with percentages instead of rem. You can still use rem but you need a better understanding, for me, the width is much easier than rem, and finally, try to read some blogs about media queries. They might help you to clear your concept more. you can find a responsive site video on freecodecamp youtube channel.

    Don't forget to give a like and mark this helpful if my comment is helpful to you!!

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