In 1.5.1, we have 2 places to regenerate CSS now. Even though the 2nd regenerate CSS is for custom breakpoints. Anyway, is that necessary? It might make us confuse especially new users.
What do you guys think?
Any feedback is welcome.
2 Likes
Is there a reason this isn’t done automatically when saving?
Some builders(at least Oxygen, Zion and Divi have it) have such option for regenerating CSS. But I think it is unnecessary to have two CSS Regerators to serve different purposes, in my opinion.
Semi-related with regards to a request to automatically regenerate on updates: Automatically regenerate CSS when updating Bricks versions
I just hit “Regenerate CSS” in the “General” tab thinking it would create and regenerate all my stylesheets in my dev environment and couldn’t work out why no stylesheets were created and there were no references to them in the HTML. 10 minutes later I found/rediscovered the other “Regenerate CSS” button under the performance tab.
So yes, it’s confusing. At least it caught me out. I’d expect both buttons to do the same thing.
1 Like