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

ConfirmPopup: Not positioned correctly when not used inside <button> #6525

Closed
marc-bq opened this issue Oct 4, 2024 · 1 comment · Fixed by #6591
Closed

ConfirmPopup: Not positioned correctly when not used inside <button> #6525

marc-bq opened this issue Oct 4, 2024 · 1 comment · Fixed by #6591
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@marc-bq
Copy link

marc-bq commented Oct 4, 2024

Describe the bug

ConfirmPopup component is rendered in wrong place when not used inside tag.
After clicking on the same element a second time while the ConfirmPopup is still displayed, then is rendered in the correct place.

Reproducer

https://stackblitz.com/edit/igcfdm?file=src%2FApp.vue

PrimeVue version

4.0.7

Vue version

3.x

Language

TypeScript

Build / Runtime

Vite

Browser(s)

Chrome

Steps to reproduce the behavior

  • Click on trash icon or Label to see how the element is rendered in a wrong place
  • Click a second time without closing the popup to see how is rendered correectly.
  • Click on the Button or Star icon to see how is rendered correctly on the first click (both elements are inside a button tag)

Expected behavior

ConfirmPopup renders just below the clicked element

@marc-bq marc-bq added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Oct 4, 2024
@tugcekucukoglu tugcekucukoglu added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Oct 4, 2024
@eneeio-nm
Copy link
Contributor

I would say for accessibility reasons you should only ever attach click events to buttons, otherwise (without a lot of additional code) it degrades the experience for users who prefer navigating with keyboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
3 participants