Overview
Simulate a mobile keyboard while developing responsive pages.
Mock Keyboard fills a gap in Chrome DevTools Device Mode. Chrome already emulates screen size, DPR, and touch reasonably well, but it does not emulate the mobile software keyboard in a way that is useful for everyday responsive UI work. That becomes a problem when building interfaces that depend on keyboard-driven viewport changes, including search bars, chat inputs, bottom docks, maps, and layouts tied to visualViewport. Mock Keyboard adds a DevTools panel that works alongside Chrome’s existing responsive device workflow. After enabling Device Mode, open the Mock Keyboard panel, turn the simulator on, and focus an input. The extension renders a mock Android keyboard overlay and exposes simulated viewport changes to the page so responsive layouts can react more like they would on a real mobile device. What it does: - Adds a Mock Keyboard panel inside Chrome DevTools - Shows a Pixel-style Android keyboard overlay - Opens and closes when editable fields gain or lose focus - Exposes keyboard-related viewport changes to page code - Helps debug mobile UI behavior without constantly switching to a physical device Current limitations: - The keyboard is visual only right now - It does not type or behave like a fully interactive IME yet - It is a simulator, not full mobile browser emulation
Details
- Version0.2.0
- UpdatedApril 7, 2026
- Offered byChrisMacSEA
- Size276KiB
- LanguagesEnglish
- Developer
Email
cmac2992+chrome@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site
