Marc Durdin 88e5bb8cdd fix(web): doModifierPress was testing against wrong device ... The doModifierPress function was testing against the 'actual' device rather than the virtual device, which meant that in the web debugger on a desktop, testing a touch device, it was effectively testing against the desktop device data rather than the simulated touch device data. I did not observe any significant differences in behaviour between the two modes. So I am not 100% confident that this change is necessary. But it is a little concerning that there was a mismatch here.		2022-11-07 07:01:50 +11:00
..
input-processor	fix(web): avoid reset for touch system keyboard	2022-11-07 06:43:39 +11:00
keyboard-processor	fix(web): doModifierPress was testing against wrong device	2022-11-07 07:01:50 +11:00
keyman-version	fix(developer): publish @keymanapp/keyman-version to npm	2022-11-02 13:33:24 +11:00
lm-message-types	chore: remove unnecessary package-lock.json files	2022-05-16 14:47:58 +10:00
lm-worker	change(common/models): adds optional 'testMode' param to LMLayer config	2022-10-31 09:34:22 +07:00
recorder	chore(common): builder_start_action wildcard support	2022-10-12 13:28:37 +11:00
sentry-manager	chore(common): more bin bashes	2022-07-25 16:03:22 +10:00
utils	feat(common): builder dependency support	2022-10-12 12:50:26 +11:00
.gitignore	chore(web): move lm-worker into its own folder	2022-04-14 15:33:23 +10:00