New issue
Advanced search Search tips

Issue 745263 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: 2017-08-01
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

execCommand('copy') doesn't work after many previous subsequent function calls.

Reported by manuelch...@gmail.com, Jul 18 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
I'm not sure how to reproduce this since my application does a lot of things. But I have a series of commands, which are calls to functions, in a function triggered by a mouse click. If one of the functions uses execCommand('copy') it works except when there are a lot of functions before it. Basically, after a lot of processing execCommand fails to work. I don't know if this is a bug or a security feature. 

What is the expected behavior?
-

What went wrong?
-

Did this work before? N/A 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version:
 
Requesting some one from blink team to take a look in to this issue.

Thanks!
Components: -Blink Blink>Editing>Command
Labels: Needs-Feedback
NextAction: 2017-08-01
Can you indicate what is "a lot of processing" in terms of time?

execCommand specifically Copy is subject to a user gesture being processed.  So that means up to 1 second after the mouse click you can call execCommand but after that it will fail.

Could it be that you are hitting this User Gesture timeout?
I made some test, and it's taking around 595ms before it gets to the execCommand line. It's a calculator application and there are over 700 inputs that need to be evaluated by the math.js library, plus some html updates, before it reaches the execCommand line.
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 18 2017

Cc: dtapu...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Update: It's actually working inside the 595ms period, since I recently refactored my code and it runs faster now. I'm assuming before it was over 1s.
Status: WontFix (was: Unconfirmed)
Closing, working as intended.
Just to know,  do you know why the User Gesture timeout is just 1 second?
The NextAction date has arrived: 2017-08-01

Sign in to add a comment