You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/09/11 17:11:00 UTC

[jira] [Commented] (NIFI-6639) Consistent checkbox and associated field behavior.

    [ https://issues.apache.org/jira/browse/NIFI-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927818#comment-16927818 ] 

ASF subversion and git services commented on NIFI-6639:
-------------------------------------------------------

Commit 250e1b0297c353086e593ea14b6ee2f5f32eebce in nifi's branch refs/heads/master from Scott Aslan
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=250e1b0 ]

[NIFI-6639] consistent ux for checkboxes and their correspoinding field

This closes #3706


> Consistent checkbox and associated field behavior.
> --------------------------------------------------
>
>                 Key: NIFI-6639
>                 URL: https://issues.apache.org/jira/browse/NIFI-6639
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core UI
>            Reporter: Scott Aslan
>            Assignee: Scott Aslan
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The property table editor now clears out the value of the editor and disabled it when the "Empty string set" checkbox is checked. When that checkbox is unchecked if we know the previous value we repopulate the field. There is an opportunity throughout the application to provide a similar UX. 
>  * Create/Edit Parameter
>  * variable registry
>  * others???



--
This message was sent by Atlassian Jira
(v8.3.2#803003)