[jira] [Commented] (NIFI-343) Shift clicking certain elements causes a new window to pop up

["Matt Gilman (JIRA)" <ji...@apache.org>]

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

Matt Gilman commented on NIFI-343:
----------------------------------

This issues appears only using FireFox. It is likely happening because images in SVG use a href attribute for referencing the image [1]. My guess is that Firefox will interpret the Shift click on any element with an href attribute as a request to open a link in a new page.

I had actually already addressed this issue (by preventing default) on click for svg images. However, when the control character changed from ctrl to shift this was overlooked.

[1] <image xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="images/bgProcessorStatArea.png" width="294" height="58" x="8" y="35" class="processor-stats-preview" style="display: block;"></image>

> Shift clicking certain elements causes a new window to pop up
> -------------------------------------------------------------
>
>                 Key: NIFI-343
>                 URL: https://issues.apache.org/jira/browse/NIFI-343
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 0.1.0
>            Reporter: Dan Bress
>            Priority: Minor
>
> If I am zoomed out on the graph enough that I cannot see the text on a processor, then shift click the processor a new window with the image of the processor pops up.  This is less than ideal because "shift-click" is the mechanism for selecting multiple graph elements that may not be near one another.
> This also seems to apply to:
> * Processor Groups in the graph
> * Funnels in the graph
> * The icon on an input or output port on the graph
> * Most of the ProcessorGroup box on the graph
> * Most of the RemoteProcessorGroup box on the graph
> * Bulletins on a processor



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)