As I checked with FF, it seems it fails. but it’s all about luck. If you set min as none(anything) try to rerun the test several times and hope the SASS goes before FCC test hit(it’s completely random, you just need luck about it)
I tried with Chrome(Version 67.0.3396.99 (Official Build) (64-bit)) and Firefox(Version 67.0.3396.99 (Official Build) (64-bit)) on Fedora 28 with no luck and found this thread. I tried clearing the cache, tried setting the minimum font size in both browsers, tried removing spaces from the code to match the challenge and was never able to pass tests. I moved to another computer entirely and was able to pass the tests there. I’ll try to remember to update this post with the Chrome version from that computer but the other differences are network speed(passed on a faster machine) and OS(passed on Windows 10, could not on Fedora 28). Hope that helps.
Frustrating these SASS challenges are all buggy. Wish I had the skills and knowledge to help fix. But “try this browser”, “add space here”, “remove a space here”, “spin around 3 times before hitting the submit button” (okay I made that up). Really not acceptable solutions and I’ve spent 10 times longer than it should have taken to get things to work. Very frustrated…
You are not reproducing the bug correctly. You have to set the minimum font size above the font size the test is looking for. It can happen with other challenges as well that depend on browser minimum font size (issue with PR).