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

Responsive HTML-CSS-JS- Interactive pricing component solution

Hugo•430
@HugoMoncada
A solution to the Interactive pricing component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi. I would take any advice regarding how I managed my CSS. I know my JS is not DRY how would you change things ?? thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi Hugo, I think you did a great job here with the range slider, and everything's working well for me. What's especially good is that I could use this with the tab key also, which makes this a great app for screen reader users.

    About the JS, I'd suggest using textContent instead of innerHTML since you only have plain text and no HTML to actually be parsed. The code does look a bit clunky right now with the switches and the repetition; what I'd do is, I'd try having all the info as an object instead, and then write a function to bring the object in. It will look something like this:

    const dataMap = { 
         "0" : {
            views: "10",
            unit: "K",
            price: 8 
         },
         "25" : {
            views: "50",
            unit: "K",
            price: 12 
         },
        "50" : {
         // info here
         },
         // ... complete the rest here
     }
    

    You can then use the following function in your event listeners and in other functions:

    function displayInfo (rangePosition, checked) {
        const info = dataMap[rangePosition]
        const price = checked ? info.price * 0.75 : info.price // this calculates the discount if "checked" is true
    
        views.textContent = info.views; 
        document.querySelector(".views-letter").textContent = info.unit; 
        price.textContent = price.toFixed(2).toString() 
    }
    

    You can experiment with it a bit, and see whether this can help you shorten the lines in your JS!

    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 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