lambdalisue/jupyter-vim-binding

Virtual keyboard doesn't appear

Open

#144 opened on May 1, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (2,062 stars) (139 forks)batch import
help wanted

Description

Summary

On mobile, clicking on a section enters normal vim mode, but there is no keyboard to change to insert mode. (No escape button anyway)

Environment

  • Operating system : Ubuntu bionic docker image
  • Web browser : Android Chrome 74
  • Version or revision of Jupyter Notebook : 4.4.0
  • Revision of jupyter-vim-binding : (e.g. 5a057d6)

Behavior

Expected

Actual

Step by step procedure

  1. Start local Jupyter Notebook by jupyter notebook
  2. Access http://localhost:8888/
  3. etc.

What you have done to solve the issue

For example, the behavior is confirmed with Firefox 44.0.2 and Google Chrome xx.xx.xx and could not be reproduced in Firefox but Chrome or what ever.

Remarks

If any

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic knowledge of Vimfamiliarity with Jupyter Notebook
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
First, examine the repository's source code (likely in JavaScript) to understand how keyboard events are handled, especially for mobile. Check if there's any existing handling for virtual keyboard or if the issue is related to the `CodeMirror` or `Jupyter` integration. Look at similar closed issues or pull requests. Since the issue is stale, comment to ask the maintainer for updated information or if the problem still exists. Investigate if a simple fix like adding a focus event or triggering the keyboard programmatically is feasible.