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
dpitois opened this issue
Jul 10, 2023
· 1 comment
· Fixed by #814
Labels
bugAn issue describing unexpected or malicious behaviour.confirmedThis label indicates that the issue has been reproduced and verified by the core team.released
Focus may be done, or not
a. Most of the time it is OK when <ClickLogger /> has a duration above 50ms
b. Maybe the focus is missing when the component displays a duration between 30 and 40ms
Note: the durations above are not accurate, sometime it works when being in the 30-40ms range, and sometime it does not work when above (like 130ms for example).
The provided repo and sandbox help to reproduce the bug based on the click duration, but in our implementation based on Custom Element and a React wrapped creating these elements, the bug is more easily reproduced.
Because it is an internal project, it can not be shared in public, but if needed, we can try to get in touch with Merck internal tools like Teams to show the bug.
The text was updated successfully, but these errors were encountered:
dpitois
added
bug
An issue describing unexpected or malicious behaviour.
triage
An issue that needs assessment to determine its validity and urgency
labels
Jul 10, 2023
borisdiakur
added
confirmed
This label indicates that the issue has been reproduced and verified by the core team.
and removed
triage
An issue that needs assessment to determine its validity and urgency
labels
Jul 10, 2023
Background: It looks like the Tether enable method returns before the actual popper element is visible. So we need to "wait" for it to become visible before setting the focus on the filter input element.
Fixes#813
Background: It looks like the Tether enable method returns before the actual popper element is visible. So we need to "wait" for it to become visible before setting the focus on the filter input element.
Fixes#813
## [5.6.4](v5.6.3...v5.6.4) (2023-07-11)
### Bug Fixes
* **ld-select:** wait for popper to be visible before focusing filter ([ce8419d](ce8419d)), closes [#813](#813)
bugAn issue describing unexpected or malicious behaviour.confirmedThis label indicates that the issue has been reproduced and verified by the core team.released
Prerequisites
Liquid version
5.5.0
Framework bindings
React
Current behavior
Sometime, the focus is not done, and the bug can be observed when user clicks quickly on the LdSelect.
Expected behavior
The focus should always be done.
Steps to reproduce
Available sandbox on CodeSandbox
a. Most of the time it is OK when
<ClickLogger />
has a duration above 50msb. Maybe the focus is missing when the component displays a duration between 30 and 40ms
Note: the durations above are not accurate, sometime it works when being in the 30-40ms range, and sometime it does not work when above (like 130ms for example).
Code reproduction URL
https://codesandbox.io/p/github/dpitois/liquid-select-focus-bug/main?file=/README.md:1,1&workspaceId=bd142dc9-6e08-409c-9537-d407ff1d0ee3
Additional information
The provided repo and sandbox help to reproduce the bug based on the click duration, but in our implementation based on Custom Element and a React wrapped creating these elements, the bug is more easily reproduced.
Because it is an internal project, it can not be shared in public, but if needed, we can try to get in touch with Merck internal tools like Teams to show the bug.
The text was updated successfully, but these errors were encountered: