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

Responsive interactive pricing component with progress bar

pure-css, bem
Djamel1133•910
@Djamel1133
A solution to the Interactive pricing component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

not proud, but happy to keep practicing and dealing with different difficulties, both in terms of programming and design.

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

Dealing with different elements (progress bar, toggle button) to udpate data but there are solid js documentation.

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

How can I handle window resizing and get the correct position of the progress indicator? Any help you can offer would be greatly appreciated.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Asilcan Toper•2,960
    @KapteynUniverse
    Posted 8 months ago

    Hey Djamel1133, i am guessing the reason of your question is you saw that little bug, when you change the screen size after interacting the progress bar, its position stays same but because of the card width changing it looks like moving away.

    I can't change JS on my side, probably because of the DOMContentLoaded. So i can't test it if it is correct but can you try to change indicator position as percentage with this slider.style.left = ${progressPercentage}%

      document.addEventListener("mousemove", (e) => {
        if (isProgressing) {
          // Get container dimensions
          const rect = progressContainer.getBoundingClientRect();
          // Calculate the new position of the slider
          let offsetX = e.clientX - rect.left;
          offsetX = Math.max(0, Math.min(offsetX, rect.width - sliderWidth)); // respect bounds
          // Update the slider position
          slider.style.left = `${offsetX}px`;
          // Update the progress bar width and slider position
          const progressPercentage = (offsetX / rect.width) * 100;
          progressBar.style.width = `${progressPercentage}%`;
          slider.style.left = `${progressPercentage}%`;
        }
      });
    
    Marked as helpful
  • Yacoub AlDweik•3,540
    @YacoubDweik
    Posted 8 months ago

    Hey! Good job buddy!

    When you resize the window you should call that function to calculate and build the correct layout, something like this:

    // Function to handle window resize
    
    function handleResize() {
        // Add your code here to execute when the window is resized
        console.log('Window resized!');
    }
    
    // Event listener for window resize
    
    window.addEventListener('resize', handleResize);
    

    Keep it up!

    Marked as helpful
  • Djamel1133•910
    @Djamel1133
    Posted 8 months ago

    Hi, @KapteynUniverse

    I added the line of code you recommended and, bam, it works! I no longer have any issues with window resizing and I don’t need to handle the window resize event. Very clever, it was just a matter of updating the position of my slider.

    I've been waiting for your comment for a while, and you came at the right moment. Thanks a lot, for me and for the community. You are a valuable help 🙏🙏🙏.

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

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