
Security News
New React Server Components Vulnerabilities: DoS and Source Code Exposure
New DoS and source code exposure bugs in React Server Components and Next.js: what’s affected and how to update safely.
react-custom-virtual-keyboard
Advanced tools
A simple, fully customizable, responsive and complete virtual keyboard for React
A simple, fully customizable, responsive and complete virtual keyboard component for integrate with React.
For a good functionality of this package, the installation will need the following additional packages:
"react": "^16.8.6"
"lodash": "^4.17.15"
Use the package manager npm to install the keyboard:
npm install --save react-custom-virtual-keyboard
In general, the keyboard wait a target property, and this must be a DOM node element from the document. It's recommended to save this node for example in the state of you main component, and update this value in the focus (set the target) and blur (unset or null the target) events of your input fields.
The theme property is used to style your keyboard with one of the preset stylesheets, the available themes are:
There is so many use cases to cover with this package. One of this are a mobile-like behaviour, the keyboard is opened once you tap or click over an input element. if you unfocus (blur) the element, the keyboard must be hidded. In this case, you must use the following properties:
import VirtualKeyboard from 'react-custom-virtual-keyboard';
// ...
render() {
return (
// ...
<VirtualKeyboard
openAuto
closeAuto
target={this.state.YourElementTarget}
theme={'console'}
/>
);
}
// ...
Another way is to give to the user the possibility of choice where to show or hide the keyboard, but the event of the pressed key works only if the prop target is set:
import VirtualKeyboard from 'react-custom-virtual-keyboard';
// ...
render() {
return (
// ...
<VirtualKeyboard
withToggleButton
target={this.state.YourElementTarget}
theme={'console'}
/>
);
}
// ...
Even you can combine the previous property to have a full use keyboard, but be careful, the closeAuto property doesn't work alone.
Using in mobile sites, when you focus an input element, the default system keyboard is invoked, and there's not a default way to prevent this. There's a way to solve this issue but require to use read-only input components and use styles to indicate the currently focused element for the user. See this StackOverflow question for more details.
FAQs
A simple, fully customizable, responsive and complete virtual keyboard for React
We found that react-custom-virtual-keyboard demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
New DoS and source code exposure bugs in React Server Components and Next.js: what’s affected and how to update safely.

Security News
Socket CEO Feross Aboukhadijeh joins Software Engineering Daily to discuss modern software supply chain attacks and rising AI-driven security risks.

Security News
GitHub has revoked npm classic tokens for publishing; maintainers must migrate, but OpenJS warns OIDC trusted publishing still has risky gaps for critical projects.