-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GrapheneForms: Smallcombo allows limited interactivity when "enabled":false #98
Comments
The same behavior is also valid for the User type fields. Please see the additional comments below: Description When a SmallCombo type and User type field are set as not-editable field in their conditions, they're still editable field and they look like enabled fields. If the section that has smallcombo box or user in it is set as a non-editable, then they both look like disabled, such as a non-editable hover item, etc, but they can be selected, edited, etc. Feature / Subsystem To Reproduce
Console Errors Link(s)
Additional context If you need additional links/ explanation, you can contact to me @alikemaltanriverdi |
@Cloverstone -- Are you able to "fix" this issue in Graphene without doing a full patch to the underlying gform library? We're having issues with this, as effectively any combobox in any workflow is editable, even when it appears that it is not. We have a couple workflows which will require this to be addressed in the next couple weeks. (April 15th) |
I have had a fix in development for a while - I will look into the
possibility of it being a stand alone patch.
…On Mon, Mar 29, 2021 at 3:54 PM Tim Cortesi ***@***.***> wrote:
@Cloverstone <https://github.com/Cloverstone> -- Are you able to "fix"
this issue in Graphene without doing a full patch to the underlying gform
library? We're having issues with this, as effectively any combobox in any
workflow is editable, even when it appears that it is not. We have a couple
workflows which will require this to be addressed in the next couple weeks.
(April 15th)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMBGELHMRQSXLAR5XYAWZDTGDLGLANCNFSM4U5A3OIA>
.
|
@Cloverstone yeah -- that's what I had thought, but a standalone patch would be great given the current reality. thanks. |
@Cloverstone it seems like this issue had been resolved, you can close this issue anytime you'd like. I just tested it in the production, and it was behaving as expected for both the workflows and the microapps |
It appears that there remains some limited interactive functionality on "smallcombo" form fields even when "enabled" is set to false.
See the attached example. In that situation, there is a "file" type which, when the down arrow is clicked, allows some limited interaction. You can't actually change the value, but it has lead to some user confusion thinking that the field is in fact editable (when it is not).
Here's another example of a normal smallcombo which is not editable:
The text was updated successfully, but these errors were encountered: