I've got a button I'm trying to use to toggle a basic boolean variable, so I can make a prompt become visible--super basic. The button and other components I've used to replicate this button's OnSelect() behavior aren't actually committing the UpdateContext() function when it's inside the form's custom data card. If I cut and paste the button or similar components to be outside the data card, regardless of whether it's still inside the parent form or totally outside floating over everything, OnSelect() starts updating the variable correctly. I'm not changing any of the button's properties, literally just pasting a copy of it outside the data card.
Other properties of these components are also being screwy in a similar pattern. For example, I set up a label to display if the variable's current contents, so I could verify whether the UpdateContext() function is working. I set this label to have a hover fill, because I noticed the button's hover fill wasn't behaving right and wanted to see if it was a quirk of the button tool or if other components would behave the same. Both label and button won't actually change color in response to hovering, while inside the datacard. If I copy/paste the label or button outside the datacard, suddenly the hover fill works.
Weirdly, the hoverbordercolor property of the exact some components DO respond inside the data card, even though he hover fill does not.
I've tried to make sure there isn't another component higher up in the layering that could be blocking my mouse from interacting with these things correctly. I've verified that the display mode is simply set to edit and isn't referencing the parent's mode etc. that it's inheriting. And I've been able to use buttons inside data cards in other powerapps in the past without a problem
Did something change? Is there another property I'm not aware of that could be affecting these components?
