Microsoft Edge Browser Not Accepting Scanned Input from Zebra Trigger Button

When using the scan trigger button on Zebra Android devices with the Microsoft Edge browser, the scanned barcode does not paste into the active input field. The same workflow functions as expected in the Google Chrome browser.

Additionally, pressing the rear scan trigger button may cause the browser to switch tabs instead of initiating a scan, which interferes with scanning operations.

Device: Zebra Android devices

Browser: Microsoft Edge (affected)

Zebra StageNow (used for configuration)

• Scan trigger button does not input barcode data into the Microsoft Edge browser.

• Rear scan trigger button switches tabs in Microsoft Edge instead of initiating a scan.

• Google Chrome browser accepts scanned input as expected.

Microsoft Edge on Android interprets the back scan trigger button as a navigation key, not as a scan initiation key. Since there is no available setting in Microsoft Edge's managed app configurations to modify this behavior, the default scan key mapping conflicts with Microsoft Edge’s key handling.

The issue was resolved by remapping the scan trigger action to the front scan button only using Zebra's StageNow tool.

Resolution Steps using Zebra StageNow:

1. Launch StageNow and create a new Profile.

2. Choose MX version 9.0 or higher.

3. Select KeyMapping Manager as the CSP.

4. In KeyMapping Manager, add a new key remapping:

• Choose a Key to Modify: Gun Trigger

• Key Behavior: Send key-code

• Key-Code: Scan

For detailed key codes and options, refer to Zebra's documentation: 

Scanning in Microsoft Edge Browser Switches Tabs and Does Not Scan on Android 14