mdn / mdn/browser-compat-data

html.global_attributes.inputmode - Imputmode=none shows keyboard on any keypress on Chrome

Open
#20,757 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:chrome_android data:html needs browser bug
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Browser bug (a bug with a feature that may impact site compatibility)

What information was incorrect, unhelpful, or incomplete?

Nothing, it's a browser bug, having imputmode=none wouldn't show the keyboard, but using the barcode reader of an attached keyboard would make the keyboard popup.

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet)

What did you expect to see?

imputmode=none won't make software keyboard show

Did you test this? If so, how?

Yes, on our devices, we have a WMS and we relied on this feature to hide the soft keyboard and use the device's or attached barcode scanner.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

Chrome 116.0.5845.173
Android 12; M2012K11AG Build/SKQ1.211006.00

MDN URL

https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/inputmode

MDN metadata
MDN page report details
  • Query: html.global_attributes.inputmode
  • Report started: 2023-09-20T10:15:23.935Z

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the MDN inputmode page and its html.global_attributes.inputmode compatibility entry. Reproduce the reported behavior on the specified Android and Chromium versions, then determine whether the browser compatibility data needs an update; done means the behavior and any resulting data change are supported by current evidence.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.