GitHub user malayhm opened a pull request:

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

    ZEPPELIN-2527 Changed editor cursor to thin

    ### What is this PR for?
    Previously, it's hard to recognize the cursor since it was too thick. After 
this PR, it will show the cursor same as other input boxes for consistency.
    
    See the attached GIFs for comparison.
    
    ### What type of PR is it?
    [Improvement]
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-2527
    
    ### How should this be tested?
    
    1. Build: mvn clean package -Denforcer.skip -DskipTests -Drat.skip
    2. Open a paragraph
    3. Check the cursor
    
    ### Screenshots (if appropriate)
    Before
    
![cursor-change-pr-before](https://user-images.githubusercontent.com/1881135/27830832-cd55ec8e-60e5-11e7-8a0e-f75caecaba30.gif)
    
    After
    
![cursor-change-pr](https://user-images.githubusercontent.com/1881135/27830837-d01fba30-60e5-11e7-8722-8056f7abaebc.gif)
    
    
    ### 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/malayhm/zeppelin ZEP-2527

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

    https://github.com/apache/zeppelin/pull/2462.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 #2462
    
----
commit e45f23b3a0acb7f05c4d559d7abf319a125549e3
Author: Malay Majithia <mmajit...@qubole.com>
Date:   2017-07-04T12:50:50Z

    ZEPPELIN-2527 Changed editor cursor to thin

----


---
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