You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated from 1.1.16 to 1.2.1 and encountered this new behavior. It can be reproduced on the current demo site (reproducible as of 13 January 2017).
Steps
On the typeahead page of the ng2-bootstrap demo site, go to the Static array section and enter new
(A few state names should appear in the dropdown.)
Make sure not to hover the mouse anywhere over the dropdown list. Then click anywhere outside the input box and the dropdown.
(The dropdown should go away.)
Repeat Step 1.
This time around, hover the mouse cursor over any of the state names in the dropdown.
Click anywhere outside the input box and the dropdown.
Behaviors
After Step 5:
In 1.1.16, the dropdown goes away.
In 1.2.1, the dropdown does not go away.
I can't find notes on whether the 1.2.1 behavior is intended as designed. As a user, however, I prefer 1.1.16 behavior as the better one. Hovering over an item in the typeahead dropdown should not prevent the dropdown from going away on mouse blur.
It seems that in 1.2.1, TypeaheadDirective.onBlur(), the this._container.isFocused property is returning true when the component should no longer be in focus.
The text was updated successfully, but these errors were encountered:
I updated from 1.1.16 to 1.2.1 and encountered this new behavior. It can be reproduced on the current demo site (reproducible as of 13 January 2017).
Steps
new
(A few state names should appear in the dropdown.)
(The dropdown should go away.)
Behaviors
After Step 5:
I can't find notes on whether the 1.2.1 behavior is intended as designed. As a user, however, I prefer 1.1.16 behavior as the better one. Hovering over an item in the typeahead dropdown should not prevent the dropdown from going away on mouse blur.
It seems that in 1.2.1,
TypeaheadDirective.onBlur()
, thethis._container.isFocused
property is returningtrue
when the component should no longer be in focus.The text was updated successfully, but these errors were encountered: