Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #51270
Closed (moved) (moved)
Open
Created Sep 08, 2018 by Markus Schlichting@madmas

External keyboard keys don't work on iOS (Chrome, Safari)

Summary

When using an external keyboard with iOS devices to edit something in Gitlab (e.g. Code in the WebIDE or descriptions for MergeRequests), the arrow keys and other functions keys down don't have any effect.

Steps to reproduce

  • Open GitLab on a iOS device with an external keyboard attached.
  • Navigate to edit a file
  • try to use the arrow keys to navigate through the file
  • nothing happens :(

What is the current bug behavior?

Editing does not work as expected.

What is the expected correct behavior?

Being able to navigate around with the arrow keys.

Results of GitLab environment info

reproduceable on current gitlab.com instance

Possible fixes

A possible fix is to use the "contenteditable" attribute in the editor. Some research shows that the issue seems to originate from the monaco-editor. So, the two options are to fix it there or to have it patched when integration it into gitlab.

https://github.com/Microsoft/monaco-editor/issues/293#issuecomment-379096075

Similar issue in RStudio (not using Monaco editor): https://github.com/rstudio/rstudio/issues/2186, fixed tere with https://github.com/rstudio/rstudio/pull/2508/files

Also similar issue for codesandbox: https://github.com/CompuIves/codesandbox-client/issues/507

Assignee
Assign to
Time tracking