wplit
commented
5 years ago I imagine something similar to selector detector to select the child element. The difference being the styles would get attached to the parent element, instead of being added as a (site specific) custom selector.
Then the elements can be added to design sets and shared across sites and all the added styles (including any custom CSS on child elements) would be self contained within that one sharable element.
To have pre-designed, shareable Woocommerce design sets at the moment, we'd need to include a code block in each section for custom CSS.
The other big use case for this is being able have elements that include styling for form inputs etc.
jamescrabb
goodwebdesignco
LauraHamburg
Describe the feature you'd like to see included in Oxygen. Similar to https://github.com/soflyy/oxygen-bugs-and-features/issues/214 which was talking about applying hover effects on child elements, but more generally I'm finding the need to target child elements from within the parent element, especially when using helper components, and now especially when using Woocommerce components.
Basically need a way to target child elements without using custom selectors or stylesheets (due to those not being included in design sets and therefore are unable to share between sites) & without using php to actually remove the markup.
What are the use cases for this feature? The specific use case here was trying to create some woo element variations that I could use across multiple sites. A featured product list is one example. The first thing needed was to remove (or just hide) some child elements that didn't make sense to keep, such as the sorting drop down, the 'showing all 4 results' text, and maybe the cart buttons, which aren't needed for this specific element.
Image for reference;
Oxygen UI doesn't provide the options to remove or hide these child elements, only to change colours, font sizes, borders etc. So without resorting to using selectors or stylesheets (which won't get transferred to another site) I'm stuck. I believe this will prevent people from being able to create reusable elements and design sets using these components.
I was first going to just request more options which included display settings, so we can hide any child elements in Woocommerce that we don't need.
But then I figured, if targeting child elements from inside a parent element became a thing, we wouldn't need lots of new settings, we could target them as if they were their own element. This would be more flexible than any component settings you could add.