(again) rollover behaviour on custom state
Mar 12, 2024
A while ago somebody posted a 'fix' for this issue (rollover behaviour still activating when a button is set to another state, either custom or visited) - which DIDN'T involve adding a trigger to each to say if it's in X state show X state on mouse enter - because that's nonsense haha) - it was something to do with the order in which you make the other states, or whether you duplicate them or make 'new' ones - does anyone know what it is I'm talking about?!
I was over the moon when I learned there was a non-shonky solution but I didn't put it somewhere safe and now I've forgotten!
Would be eternally grateful if anyone knows what I'm talking about cos I can't find it with search. I promise I'll save it somewhere in size 80 font this time!
2 Replies
Hi Erin, the method I've used in the past is to select all elements in the state you want to stick, then cut and then paste. I think this will then prevent the hover state showing. There is a down side, if the main element is a text field, it will no longer update with the other states when text is updated in the normal state.
Thank you! I wonder if that was it... to be honest I've stopped expecting the text to update across states. I don't know what it is about how I create buttons but it's now embedded in my process that if I change the text I have to check (and nearly every time correct) the other states