aurelia / aurelia/framework

Loosing characters in bound field when using Barcode scanner and IE

Open
#917 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
11.7k
Forks
608
PR merge metrics
No merged PRs in 30d

Description

**I'm submitting a bug report**

* **Library Version:**
aurelia-framework@1.3.0

**Please tell us about your environment:**
* **Operating System:**
Windows 7/10

* **Node Version:**
v10.8.0

* **NPM Version:**
6.5.0

* **Aurelia CLI OR JSPM OR Webpack AND Version**
CLI 1.0.0-beta.7 (Webpack)

* **Browser:**
IE 11

* **Language:**
TypeScript 2.7.2

**Current behavior:**
We have an application that is to be used in our Distribution Centers.
It has only one bound inputfield. The workstations have a Barcode Scanner that is connected via USB and which behaves as a keyboard. The characters of the scanned barcode are send to the workstation as if they were typed in. The scanner is configured to emit a carriage return at the end of the input which triggers our business logic.
The scanner can be configured to have a delay per keystroke ranging from 0-50 ms.
In google chrome we have no error whatsoever, regardless of the delay.
In IE (11) however, we see missing characters at random locations.

We have used this setup in the past using Durandal (knockout) and never had a problem.
When we set the above mentioned delay to 50 ms, the input is received completely. This is however an unacceptable delay.

**Expected/desired behavior:**
We expect to receive all characters even with a 0 ms delay (like in Chrome).

* **What is the motivation / use case for changing the behavior?**
We first had a Durandal setup. But we want to upgrade to a modern framework and Aurelia is the logical choice.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the bound-input behavior in IE 11 with the barcode scanner set to a 0 ms delay, then compare it with Chrome and with a 50 ms delay. The issue is done when every scanned character reaches the input and the terminating carriage return still triggers the business logic.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.