-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Trigger loses focus after copy event #695
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@zenorocha Any thoughts/comments on this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bump |
@adamgruber can you provide some case to reproduce this on another enviroment? |
@helderburato Why was this closed without explanation? It's only been 2 days since the request for repro. I plan to add one but even still I feel like the original question was never answered. |
Here's a repo project that illustrates this issue: https://github.com/adamgruber/clipboard-js-issue. I stand by my original statement that this was a breaking change. |
Why was this closed? it's an actual issue still... |
copying in what I wrote over in twbs/bootstrap#33894
Note that this behaviour now reverts what was fixed originally in #419 |
@zenorocha could this be reopened please? |
Note that this has now been fixed/merged #807 |
This line of code was added in v2.0.5 that caused a breaking change. I was unable to find a reason for the addition in the commit logs but the behavior is such that calling
clearSelection
no longer behaves as expected.Behavior in 2.0.4
Calling
clearSelection
returns focus to the triggerBehavior in 2.0.5+
Calling
clearSelection
returns focus to the trigger THEN is subsequently cleared by callingdocument.activeElement.blur()
Can you provide any insight on the reason for this change? It seems like a bug to me.
The text was updated successfully, but these errors were encountered: