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

fylo-data-storage-component

Maria•130
@maaghia
A solution to the Fylo data storage component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am gonna need some help to style the range input, I would be glad to receive any help so that I can complete the challenge

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Faruk Abdulganiyu•380
    @faruking
    Posted about 3 years ago

    Visit this link to help you better understand ranges styling ranges

    Marked as helpful
  • Saleem•220
    @Thesaleem
    Posted about 3 years ago

    Good job there, i guess the above suggestions should help.

  • Yokke•620
    @Jexinte
    Posted about 3 years ago

    Hey @maaghia,

    To do style the progress bar you can set a parent div which contains ::after pseudo elements it's very useful to style those kind of things.

    The parent div will be set on relative position and ::after on absolute position then you can style it like the design.

    The white circle is very easy to do I'll let you think about it you've done a good job I'm sure you will find the solution for it .

    More details here :

    :: AFTER https://developer.mozilla.org/en-US/docs/Web/CSS/::after

    POSITION ABSOLUTE , RELATIVE https://developer.mozilla.org/en-US/docs/Web/CSS/position

    In hope it helps !

  • Manoj Kumar Singh•970
    @dev-mksingh
    Posted about 3 years ago

    Hey @maaghia, good work out there, in response to your concern here is what you can do :

    1. Take a <div></div> element and set height, width and padding of it as appropriate.
    2. Nest the <div></div> element created in step 1 with another <div></div element and set height less than the parent <div></div> also use gradient background-color, again set the padding as appropriate. And set position:relative;
    3. Again nest the <div></div created in step 2 with another <div></div> element and set the
    border-radius: 50px;
    position:absolute;
    right: 0 ;
    margin-right: 5px;  
    

    Note: You might need to add some other CSS properties as per requirement, but the above step will definitely help you with the range stuff. Also there can be other ways, but in my opinion and challenge i performed the same. Hope you will find this solution helpful. Happy coding.

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

Oops! 😬

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

Log in with GitHub