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

ASF GitHub Bot commented on NIFI-5173:
--------------------------------------

GitHub user mcgilman opened a pull request:

    https://github.com/apache/nifi/pull/2692

    NIFI-5173: Fixing component selection issue in zoom handling

    NIFI-5173:
    - Removing unnecessary logic in the zoom handler since the zoom event is no 
longer triggered during onClick.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mcgilman/nifi NIFI-5173

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/2692.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2692
    
----
commit 180d911fbf72441d64064ca078706b923c0fb1b0
Author: Matt Gilman <matt.c.gilman@...>
Date:   2018-05-09T16:07:07Z

    NIFI-5173:
    - Removing unnecessary logic in the zoom handler since the zoom event is no 
longer triggered during onClick.

----


> Graph search control fails to demonstrate component selection
> -------------------------------------------------------------
>
>                 Key: NIFI-5173
>                 URL: https://issues.apache.org/jira/browse/NIFI-5173
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 1.6.0
>            Reporter: Alex Aversa
>            Assignee: Matt Gilman
>            Priority: Minor
>
> When using the graph search control to locate a component within a flow, the 
> searched item fails to render as selected on the graph. The item is 
> positioned correctly, but is not highlighted accordingly. Preliminary 
> research indicated that within the *nfActions.show* method, the 
> *selection.classed('selected',true);* is being reset by a subsequent call.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to