Fix field element blur event trickery (#59)

See https://github.com/UrbanCompass/ngc-omnibox/compare/blur?expand=1#diff-d8a178e25f29a787558002bb505a778dR59 for details

Author: josephschmitt

package.json

@@ -1,6 +1,6 @@
 {
   "name": "ngc-omnibox",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "A modern, flexible, Angular 1.x autocomplete library with limited assumptions.",
   "main": "dist/ngc-omnibox.js",
   "scripts": {

src/angularComponent/ngcOmniboxController.js

@@ -56,6 +56,20 @@ export default class NgcOmniboxController {
           $scope.$apply();
         }
 
+        // Focus/blur events are finicky, especially when the blur event fires when there's no other
+        // focus target (such as hitting the ESC key, manually calling blur(), or on mobile when
+        // hitting "Done" on the keyboard): the field can still be the focused element. This is a
+        // problem since it means if the user then immediately tries to focus the field again, the
+        // focus event won't fire (since technically the field is already focused). To combat this,
+        // we check here to make absolutely certain that the field isn't currently focused and if it
+        // is, we'll focus our main component element which a.) has a tabindex so we know it's
+        // focuseable, and b.) allows us to keep listening for more events if we need to. Also,
+        // since the element that kept focus is a child of our component element, focusing it won't
+        // call the focus event listener again, avoiding an infinite loop.
+        if (this.doc.activeElement === this.fieldElement) {
+          this.element.focus();
+        }
+
         this.onBlur({event});
       }, SUGGESTIONS_BLUR_THRESHOLD);
     }, true);