GitHub user cloverhearts reopened a pull request:

    https://github.com/apache/zeppelin/pull/1879

    [HOTFIX : ZEPPELIN-1932] paragraph blur error

    ### What is this PR for?
    When one or more hidden editors are present, clicking on the editor will 
cause a blur error.
    This means that when a paragraph is hidden through ng-if,
    Caused by calling the blur method in the absence of an editor object.
    
    ### What type of PR is it?
    Hot Fix
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-1932
    
    ### How should this be tested?
    1. create paragraph and open debug console.
    2. enable hide paragraph.
    3. page refresh
    4. click to anywhere paragraph.
    
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? no


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

    $ git pull https://github.com/cloverhearts/zeppelin 
hotfix/paragraphOnfocusEvent

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

    https://github.com/apache/zeppelin/pull/1879.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 #1879
    
----
commit 5ecfabbe45131826b597ca430ff833f0094cf482
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-11T05:30:35Z

    check editor object is undeifned.

commit 8f4d0bf9cbb02b264d095010ed0734e02869f861
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-11T10:23:38Z

    fixed readonly event error

commit 7071638f93085482b3c91837c7c369051d2d9bac
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-13T02:53:10Z

    fix show title and paragraph context issue

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to