Global Search and Num lock key and number pad

Brian Oevermann

22 août 2016 22:19

HTML5Viewer 2.6.1; Issue present in IE, Chrome, and Firefox

 

Scenario: User clicks the Global Search input box to enter a value. If the mouse pointer stays within the Global Search box or the title banner area, numbers can be entered via the number pad on the keyboard (if num lock is on). However, if the mouse pointer moves in the map window area, the number pad appears to revert to a num-lock-off state and the arrow keys begin to function, despite the input focus still being in the Global Search input box.

 

One can move back and forth between the upper banner area and the map and the functionality of the number pad changes.

 

This appears to be a usability bug. I expect that if I am entering a value with the number pad into the Global Search input box that it shouldn't matter where the mouse pointer is.

 

Do others experience this same behavior? LG, can you please fix this? It is reducing users' productivity trying to ensure their mouse pointer doesn't move.

 

If this WAS by design, can you explain the thought process regarding why?

 

 

0

• 

  Permanently deleted user

  22 août 2016 23:04

  Hi Brian, I can confirm that this is indeed a bug (GVH-7141). I'm following up with the viewer team now.

  0
• 

  Brian Oevermann

  23 août 2016 14:44

  Thank you, Jordan! Will the fix be in the next update?

   

  Also, any chance that this is also a bug for IE? :

   

  https://support.geocortex.com/customer/apex/essentialsGSCForum?sub-nav=forum&main-nav=essentials&#!/feedtype=SINGLE_QUESTION_DETAIL&dc=All_Essentials&criteria=ALLQUESTIONS&id=90660000000TSZxAAO

   

   

  0
• 

  Permanently deleted user

  26 août 2016 23:05

  I can't promise that it will be in the next update, but I've made them aware of the impact to your users. We'll do our best.

   

  As for your other question, it looks like Danny has answered it since your reply, but let me know if you'd like more information.

  0
• 

  Permanently deleted user

  16 décembre 2016 00:57

  Follow-up: this is an issue with the Esri map control itself. You can see it behave similarly in (https://developers.arcgis.com/javascript/3/samples/ed_attribute_inspector/) this sample . As a workaround, you will be able to disable keyboard navigation in configuration in HTML5 viewer 2.8 (GVH-12200).

  0

Vous devez vous connecter pour laisser un commentaire.