I do really like all the options that you get control of with Pro V2 elements, and the fact that you can save your own element presets. But there seems to be a major flaw with this design which completely undermines the very nature of cascading style sheets.
The genius of CSS is that you can change the the declarations within a given rule and it will update everything site-wide on the front end (nothing we don’t already know here). But when I use Pro’s element controls to style the element, at best all I can do is save a preset of that element, then I can apply that preset all over the site. Great. But then down the road if I want to change the look of said element and have those changes apply site-wide, there’s no way to change it all in one go like you can with good ol’ style sheets. I’d have to track down all the elements that I want to change and then update them all one-by-one with the new preset. This totally defeats the idea of style sheets altogether.
I also understand that there are global blocks too, but those only work when you want the content inside the element to be exactly the same in every instance of the global block.
If I was just assigning the element a class in Pro and then typing the CSS the old fashioned way in my Theme Options custom CSS, then at least I could make site-wide changes to that element in one go, regardless of the content within the element. But then that defeats the purpose of having all these nice element controls and presets in Pro.
Are there any plans to implement a solution for this? Where a preset or even a custom class name could be edited and the changes be applied site-wide?