Hello,
There’s a error with Bubble Standard Multiline Input.
The option “this input is disable” does not work. The input is always enabled as seen bellow:
To double check, do you have any conditional formatting applied to the multiline input? (Similar to the screenshot below).
No conditional applied.
Problem persists.
Any answers?
Have you tried running in Safe mode?
I hadn’t noticed this before, but this may be the issue. To confirm: you’re using a multiline input, but you don’t want for it to be clickable. (So, effectively, a text box).
However, you have auto-binding on the parent’s thing. Given that you don’t want this thing to be editable, there’s no reason for auto-binding in this case. Because you have auto-binding enabled, that is likely over-riding the “This input is disabled” setting.
@dan1
Hey Dan. YOu helped to discover the Problem with Bubble.
I have some Multiline inputs that autobind OK? And I need some of them to disable in certain conditions.
When enable autobindig option is ON, the option to disable the input does not work.
When enable autobindig option is Off, the option to disable the input works.
See images:
When enable autobindig option is Off, the input disables successfull:
When enable autobindig option is ON, the input does not disables:
Waiting Bubble can solve this…
Did you read Dan’s most recent reply?
Since you don’t want the element editable (you want it disabled), enabling autobind makes no sense.
So don’t do that is what he’s saying.
1 Like
Further: We get that you want to poplulate the input. Do that by connecting your stored value to the “placeholder” and “initial value” fields.
If the stored value is empty and you’d like the user to populate it, just show a different multi line input that is NOT disabled.
HOWEVER: There IS NO GENERAL BUG with autobound multiline inputs as far as I can see. They can be disabled. (I just tried it – works fine.)
As Dan suggests, some plug-in you have installed may be messing with the behavior of multi-line inputs in an undesirable way. (That’s why he suggests trying to run in safe mode and observing the behavior.)
Hey @keith, thanks for participanting and help
I tried the Safe mode for HTML and plugins, but the problem persists.
You’d have to have someone take a look at your editor view to figure out what might be the issue.
Here’s the thing I’m getting confused about in your description. You say:
But previously you had said:
That makes no sense to me. The only way you could TOGGLE the input between being disabled and enabled is to have a CONDITION on it.
So… How do you even KNOW that you can’t toggle enabled/disabled on and off? It’s just confusing to me. (I might be missing something… but I’m not aware of a WORKFLOW option to enable/disable an input.) You’d have to put a CONDITION on it like “When… some_condition_met” → This input is disabled.
Here is what you MIGHT be missing:
Note that “This input is disabled” is a CHECKBOX. By checking it, you are saying, “when some_condition_met” DISABLE the input. If you leave it unchecked, you are saying, “when_some_condition_met” ENABLE the input.
Could this be the source of your problem?
Hey,
I created new inputs with no condition (images i posted above), just to test and put here to show the issue and discuss here.
In my App i Will need after to create a condition to disable, but in the images i posted here, all inputs have no condition.
Hey Guys. I discovered the problem…
The problem is in the option Strecth to fit content.
When it is ON, the input can’t disable.
Ehen it is OFF, the input disables.
I will post a video here.
I dont know, but It seems a bug.
That’s interesting. I think I’m seeing that, too. One thing to check: even though the element is editable, I might wanna see it it ACTUALLY edits the underlying data field.
(But yeah sounds like a bug. U should submit a bug report with that video.)
Thanks for the bug report. We’ll let you know once fixed.
This topic was automatically closed after 14 days. New replies are no longer allowed.