Today I noticed this issue, when clicking on "Copy Summary", from the top-right dropdown from Perfherder's alerts. The browser console outputs this: document.execCommand(‘cut’/‘copy’) was denied because it was not called from inside a short running user-generated event handler.
What browser version are you using? I get another error when I try to do this with Chrome: TypeError: G.toLocaleFormat is not a function at U.getTextualSummary (perf.4b16002….bundle.js:48) at Hc.A.copyTextToClipboard (perf.4b16002….bundle.js:48) at fn (eval at compile (vendor.0513c80….bundle.js:41), <anonymous>:4:365) at Zc (vendor.0513c80….bundle.js:41) at Wc (vendor.0513c80….bundle.js:41) at Hc.$eval (vendor.0513c80….bundle.js:41) at Hc.$apply (vendor.0513c80….bundle.js:41) at HTMLAnchorElement.<anonymous> (vendor.0513c80….bundle.js:41) at HTMLAnchorElement.dispatch (vendor.0513c80….bundle.js:13) at HTMLAnchorElement.Za.handle (vendor.0513c80….bundle.js:13) With Firefox Nightly it works fine minus a warning: Date.prototype.toLocaleFormat is deprecated; consider using Intl.DateTimeFormat instead perf.4b1600210b5b8941ecdd.bundle.js:48:64452
I'm using Firefox. I think you have that error from Chrome.
More precise: Firefox 54.0.1
(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #3) > More precise: Firefox 54.0.1 Just tested on Firefox 54.0.1 and it works fine for me. Do you have any extensions installed which might be interfering with this?
I can no longer reproduce the regression on Firefox. (In reply to William Lachance (:wlach) (use needinfo!) from comment #4) > Just tested on Firefox 54.0.1 and it works fine for me. Do you have any > extensions installed which might be interfering with this? Yes, I have of bunch of extensions enabled. I will test this several times. If I don't see anything, I'll close this with WORKSFORME.
Component: General → Perfherder
Product: Testing → Tree Management
Version: unspecified → ---
Let's resolve this.
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.