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

🐞 - [Skeleton] Should block content selection in a Skeleton #9000

Closed
2 of 9 tasks
ajitzero opened this issue Sep 12, 2024 · 0 comments · Fixed by #9001
Closed
2 of 9 tasks

🐞 - [Skeleton] Should block content selection in a Skeleton #9000

ajitzero opened this issue Sep 12, 2024 · 0 comments · Fixed by #9001
Labels
community contribution This issue was closed by a PR from the community P3 This issue has low priority S3 This issue has low severity

Comments

@ajitzero
Copy link
Contributor

Playground Link

https://taiga-ui.dev/directives/skeleton

Description

Current behavior:

  • Try to select the content (text/images) across the skeleton section.
  • Copy with right-click context menu or Ctrl/Cmd + C.
  • We are able to select and copy content which is invisible and should be inert.

Expected behavior: User should not be able to interact with hidden/loading content.

Suggested fixes:

Angular version

Any/Latest

Taiga UI version

Latest

Which browsers have you used?

  • Chrome
  • Firefox
  • Safari
  • Edge

Which operating systems have you used?

  • macOS
  • Windows
  • Linux
  • iOS
  • Android
ajitzero added a commit to ajitzero/taiga-ui that referenced this issue Sep 12, 2024
@waterplea waterplea added community contribution This issue was closed by a PR from the community P3 This issue has low priority S3 This issue has low severity and removed state: need triage labels Sep 12, 2024
ajitzero added a commit to ajitzero/taiga-ui that referenced this issue Sep 12, 2024
ajitzero added a commit to ajitzero/taiga-ui that referenced this issue Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community contribution This issue was closed by a PR from the community P3 This issue has low priority S3 This issue has low severity
Development

Successfully merging a pull request may close this issue.

2 participants