Always used to be the case as far as I can recall, that when we use the trigger for ‘when an inputs value is changed’ that this would trigger if the input had a value and that value was deleted and then the input became unfocused. This is no longer the case.
Simple logic would dictate that if I have a value in an input and I remove that value, I changed the value.
Try out my Energizer plugin. If you look at the demo it also watches an input and can trigger anything instantly.
Thanks, I’ll take a look at it if Bubble is unable to fix the bug in a timely manner or comes back with the absurd ‘this is intended behavior’ excuse.
BTW @GH5T the plugin looks like it has tons of other great use cases as well. Thanks for putting it out.
Yeah I’ve noticed their “when an input value changes” is unreliable at points. The fact we have to wait until the user is no longer focused to get that value is sad (in vanilla).
Problem with the bug is it is not seeing the fact that removing a value is the same as changing the value even once the input is no longer focused.
Also having a bug in the multiline input element which sees an empty multiline input value as not empty and the character count coming back as 1.
Got it. Then maybe my Input Trigger might be a good alternative solution for you. Give it a try and let me know if it works for your purpose. It’s accurate and can manage multi-line input actions much easier than vanilla.
Hey Matt, does the issue happen consistently for you in any app? I ask b/c I’m unable to reproduce. It works as expected for me.
Thank you @sudsy I tested in another app and the issue is not present. And in the other app the other issue I experienced related to multiline input count is not present either. I’m going to check in the app that experiences the problem to see if an update to version is in order or not.
This was not a bug, as I’ve come to find out on my own. Bubble support had not replied within 6 days of submission and 2 days after following up with them, still have not heard back.
But in continuing to try and get the issue resolved for client, I’ve uncovered the root cause.
If you have an input that is set to ‘should not be empty’ if that input becomes empty, the trigger will not fire, but if the ‘should not be empty’ is unchecked, then the trigger does fire.
This is the same for a search box element as well, and I’d venture to guess, true for multiline input as well.
This topic was automatically closed after 14 days. New replies are no longer allowed.
