It would be great if the interactions class fields (both the existing “Affect different element(s)” field and any future hypothetical ones that would let you assign a class as an interaction event per Interaction options roadmap - Product feedback - Forum | Webflow) would accept the same complex selectors that you can assign to an object outside of interactions.
For example, if I’m styling an object outside of an interaction, I can specify something like:
… but if I’m trying to add that complex selector in the Affect different elements(s) field, it doesn’t recognize that “top” is a nested selector under “live-row” that should be available.
Maybe I’m being a bit sloppy with my selector naming and there’s a best practice for that which would make this a non-issue, but it seems like something I’d expect since the Current Selector field recognizes existing subclasses and will offer them and auto-fill them.