Browser: Chrome 110
OS: macOS / Windows / Linux / etc.
URL: Link to a page that illustrates this issue
Video: Short screen recording that illustrates this issue (free tool: jam.dev)
Hello bricks team,
If you inspect the Price range filter using the browser inspector, it will render unnecessary DOM value.
Hi Victor,
Thanks so much for your report!
You can switch between slider and input type in the filter range element. If you set it to slider, the input fields will be hidden. This is not a bug, but rather a consequence of the current implementation. Removing them entirely from the DOM might be an improvement, but definitely not a bug 
Best regards,
timmse
Yes, you are right. But if it makes sense, if the slider type is enabled, the input type will not be rendered in the DOM, right? Could this be a feature request?
