Anyone know why the ‘Continue’ button is clickable when no values are entered? When not clickable, the button takes the following style:
(FYI I have this same button working on other steps)
Both fields have ‘This input should not be empty’ selected…
The step is being printed, so we can see it is 2…
I thought maybe the issue was that it hadn’t strictly been ruled ‘not valid’ as nothing had been entered, but even with a dodgy email it doesn’t work…
Thoughts?
maybe something with the input format?
Check the input format for that input and try to make it “email” or “password” if it’s - “text”
Hmm don’t think that’s it, both inputs appear to be set correctly…
The behavior of the button should correlate with the workflow it’s running. Please share more about the workflow.
I ran the debugger and I get some weird behaviour when I inspect the email address field
Is valid = yes
Isn’t valid = no
How can it be valid with no characters entered, and the settings selected above…
Not sure the workflow is relevant as this is related to a element condition not evaluating to true??
Try recreating the form and see if the issue persists.
Ahhh that’s hours of work…
I’ve narrowed the issue. The first was I had an ‘and’ on the email/password condition, should be an ‘or’.
The second is that bubble doesn’t recognise a field as not being valid until you start typing in it… e.g. as soon as I enter a character in the email the condition evaluates to true:
I’ll see what anyone else has to add, but maybe I need to reverse the logic so that the button is disabled by default, and then enabled if the condition is true.
Answer is that I also need to check if the field has 0 characters…
Sooooo to fix this, I’ve had to create 4x separate conditions:
Would be so much nicer if I could do:
step is 2 and (email is empty, or email is not valid, or password is empty, or password is not valid)
I saw a release coming with parentheses but doesn’t seem like it’s out… Any bubblers out there have a neater/more compact way achieving what I need? My form has about 7 steps, and some 3-4 fileds…
I’m reusing the same ‘back/continue’ button for each step (hence the step check)… this means I’ll need to create around 30-40 conditions on the button. Would be neat if I could get this to work in one expression somehow
This topic was automatically closed after 70 days. New replies are no longer allowed.
