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

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

GitHub user scottyaslan opened a pull request:

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

    [NIFI-1904] If open, close hamburger menu on window resize

    

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

    $ git pull https://github.com/scottyaslan/nifi NIFI-1904

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

    https://github.com/apache/nifi/pull/1106.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 #1106
    
----

----


> Resizing window while Summary/Counters/etc dropdown activated causes canvas 
> to resize to original size after dropdown closed
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-1904
>                 URL: https://issues.apache.org/jira/browse/NIFI-1904
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>            Reporter: Aldrin Piri
>            Assignee: Scott Aslan
>            Priority: Minor
>
> When working with the dropwdown (this is the menu item in the top right 
> corner comprised of items such as the Summary/Counters/Bulletins), if the 
> window is resized while this is activated, it seems the original state of the 
> canvas, s0, (this is the entirety of the NiFi workspace) has its original 
> size stored.  
> During the resize, the workspace will expand/contract as anticipated as the 
> browser does, s1, but once the dropdown is closed/loses focus, the workspace 
> will then revert to the size, s0, before the dropdown was activated and 
> manipulated where it is anticipated this would stay in its adjusted state, s1.



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

Reply via email to