Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ui5-popover: wrong position after open #2556

Closed
nnaydenow opened this issue Dec 9, 2020 · 2 comments · Fixed by #2583
Closed

ui5-popover: wrong position after open #2556

nnaydenow opened this issue Dec 9, 2020 · 2 comments · Fixed by #2583
Assignees
Labels
bug This issue is a bug in the code Medium Prio TOPIC RD

Comments

@nnaydenow
Copy link
Contributor

Description

ui5-popover is not correctly positioned when the .openBy method is called twice with different opener.

Steps to reproduce:

  1. Open the isolated example: https://codesandbox.io/s/ui5-webcomponents-forked-q62mk
  2. Click the first button (could be clicked with mouse)
  3. Press tab to focus the second button
  4. Press space/tab to open the popover

4

Note:The issue is reproduced only with if you trigger action through the keyboard.

@NHristov-sap
Copy link
Contributor

Hi,

The issue is reproducible, please see example mentioned above. When the Button 1 is clicked, popover opens correctly; then, when button 2 is clicked, popover also opens correctly. The issue is reproducible only when the focus is moved with keyboard interaction (Tab, Shift+Tab), and then the popover is opened with Space/Enter - then the popover is not moved to the currently focussed button, but stays at the same.

Best Regards,
Nikolay Hristov
Github Dispatcher

@NHristov-sap NHristov-sap added the bug This issue is a bug in the code label Dec 9, 2020
@NHristov-sap
Copy link
Contributor

FYI @SAP/ui5-webcomponents-topic-rd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug in the code Medium Prio TOPIC RD
Projects
Status: Completed
Development

Successfully merging a pull request may close this issue.

3 participants