[Bug Report] v-autocomplete/v-combobox @blur behaviour
See original GitHub issueEnvironment
Vuetify Version: 2.2.20 Vue Version: 2.6.11 Browsers: Chrome 80.0.3987.163 OS: Mac OS 10.15.2
Steps to reproduce
- open console
- focus input
- check console for ‘handleFocus’
- click ‘no data’
- check console for ‘handleBlur’
- re-focus input field
- handleFocus doesn’t trigger again
Expected Behavior
v-autocomplete/v-combobox @blur
event should be triggered when the component is-focused
class is removed
Actual Behavior
v-autocomplete/v-combobox @blur
event is triggered when the input is unfocused but is-focused
class still exists
Reproduction Link
https://codepen.io/donald-ma/pen/JjYPQjX
Other comments
v-autocomplete/v-combobox @focus
event seems to be triggered when the is-focused
class is added but @blur
event triggers even if the is-focused
class is still there.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Vuetify Bug report of autocomplete with combobox ... - CodePen
URL Extension Required. When linking another Pen as a resource, make sure you use a URL Extension of the type of code you...
Read more >Autocompletes - Material Component Framework — Vuetify.js
The v-autocomplete component offers simple and flexible type-ahead functionality. This is useful when searching large sets of data or even dynamically ...
Read more >Editable Combobox With List Autocomplete Example - W3C
This example illustrates the autocomplete behavior known as list autocomplete with manual selection. If the user types one or more ...
Read more >Change Log - /dropdowns - Kendo UI for Angular - Telerik
Bug Fixes. itemDisabled not working with virtualization (#709); autocomplete: scroll input on blur: firefox; combobox: emit empty string on ...
Read more >Combobox - Lightning Design System
A widget that provides a user with an input field that is either an autocomplete or readonly, accompanied by a listbox of options....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think that this is a documentation issue, not a functionality issue. @bigbadfatman is correct. The first item in the component events API documentation indicates that the blur refers to the
<input>
, not the component. But the same documentation describes thefocus
event as referencing focus of the component, not the<input>
. Testing in the browser reveals that bothfocus
andblur
reference the<input>
element.This can be confirmed by changing @donaldma 's Codepen to log the event.type and event.target.
My suggestion is that this issue be referenced to the docs, which should be updated.
In fact, I am seeing that if there is no
no-data
slot in use, but content appears that eliminates all possible values from the select, the same behavior happens - blur happens but focus does not.