From 85282ef4ad90e33e6b0a35bdf1fe062cd262693c Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Sat, 19 Jun 2021 18:50:12 +0300 Subject: [PATCH] minor fixes --- 2-ui/3-event-details/7-keyboard-events/article.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2-ui/3-event-details/7-keyboard-events/article.md b/2-ui/3-event-details/7-keyboard-events/article.md index 6318fde2..78c4bf1f 100644 --- a/2-ui/3-event-details/7-keyboard-events/article.md +++ b/2-ui/3-event-details/7-keyboard-events/article.md @@ -149,9 +149,9 @@ The `onkeydown` handler here uses `checkPhoneKey` to check for the key pressed. As we know, the `false` value returned from the event handler, assigned using a DOM property or an attribute, such as above, prevents the default action, so nothing appears in the `` for keys that don't pass the test. (The `true` value returned doesn't affect anything, only returning `false` matters) -Please note that special keys, such as `key:Backspace`, `key:Left`, `key:Right`, do not work in the input. That's a side-effect of the strict filter `checkPhoneKey`. +Please note that special keys, such as `key:Backspace`, `key:Left`, `key:Right`, do not work in the input. That's a side-effect of the strict filter `checkPhoneKey`. These keys make it return `false`. -Let's relax it a little bit by allowing `key:Left`, `key:Right` arrows and `key:Delete`, `key:Backspace`: +Let's relax the filter a little bit by allowing `key:Left`, `key:Right` arrows and `key:Delete`, `key:Backspace`: ```html autorun height=60 run