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
Hit enter, then try to move up and down with the keyboard.
Expected result
Able to move up/down
Actual result
The item is not focussed.
Querying document.activeElement shows that the focus is still on the trigger.
Opening the menu a second time makes the issue disappear.
This is because the first render of the popover doesn't become visible directly and has an arbitrary delay defined by requestAnimationFrame, see my upstream report for details: Akryum/floating-vue#661
Workaround
Depending whether upstream will accept a PR that emits a new event or not, there are other possible workarounds:
Extend our Popover component to monitor the DOM periodically in the @show handler, and only once the .open class appears, trigger another event like afterShow. Only do so if there's a handler set there.
Like 1 but do the periodic monitoring in the Actions class
Like 2 but simply retry focussing the first element if it failed
So far I prefer approach 1 as a temporary workaround until v-tooltip is fixed upstream.
The text was updated successfully, but these errors were encountered:
Steps
Expected result
Able to move up/down
Actual result
The item is not focussed.
Querying
document.activeElement
shows that the focus is still on the trigger.Opening the menu a second time makes the issue disappear.
This is because the first render of the popover doesn't become visible directly and has an arbitrary delay defined by
requestAnimationFrame
, see my upstream report for details: Akryum/floating-vue#661Workaround
Depending whether upstream will accept a PR that emits a new event or not, there are other possible workarounds:
Popover
component to monitor the DOM periodically in the@show
handler, and only once the.open
class appears, trigger another event likeafterShow
. Only do so if there's a handler set there.So far I prefer approach 1 as a temporary workaround until v-tooltip is fixed upstream.
The text was updated successfully, but these errors were encountered: