it would be great if this would not be needed by default.
The UCSS function has no default parameters that exludes any default CSS from being excluded, so you have to specify which CSS has to be excluded manually.
Anything else would be dangerous and would provoke uncontrolled behavior. An automated exclusion would be good, but that assumes that every WordPress installation uses the same CSS. You certainly can’t imagine that, can you?
I don’t understand that argument. There are other fields that do have default settings. Take the lazy load class name exclusion for example…
Lazy load is not UCSS. Each function is different, so please follow my advice to specifiy which CSS has to be excluded.
… so please follow my advice to specifiy which CSS has to be excluded.
Yes, like I said, we already did that. No worries 🙂
It’s just that the native Navigation block has been around for a while now and is used in the latest 3 default themes. Many others will be using it in sidebar, footer or custom header or even just in page content while not being aware that it (in combination with UCSS) is broken for mobile visitors… And excluding the file remains sub-optimal.
Apparently, the UCSS filter process does not “see” the use of these CSS classes and filters them out. It’s probably because these classes are set through javascript? But however you would like to spin that or lay blame, it remains “not good” in my view. That’s all 🙂