@traez's Interactive pricing component solution, using JavaScript etal

Solution retrospective
1] Continued use of Objects to hold data. Nothing much else too new.
2] Exposure to new concepts in CSS (slider and toggle). To save time and avoid diving into deep CSS I decided against designing Input Range Track and Thumb ("The slider", as a different styling would be needed for each browser: Chrome, Firefox, Microsoft, etc).
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Trae Zeeofor's solution.
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