New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 779961 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression: Weird glimpse is seen after giving print command on chrome://media-internals.

Reported by db...@etouch.net, Oct 31 2017

Issue description

Chrome Version: 64.0.3253.3 Revision d5f4ba12a6c29b1b49da50663e51d7d6d2dad88e-refs/branch-heads/3253@{#5}(32/64bit)
OS: Windows (7,8,10),Linux (14.04 LTS),Mac OS X(10.12.6,10.13.1)


What steps will reproduce the problem?
(1)Launch chrome and navigate to chrome://media-internals/
(2)Click on ‘Copy to Clipboard’ button and give Print command,observe.

Actual: Weird glimpse is seen after giving print command.

Expected: 1.No such a glimpse should seen after giving print command or
          2.Print preview should not get opened.

This is regression issue, broken in ‘M 61’ and below is manual bisect info:
Good build:61.0.3129.0
Bad build:61.0.3131.0

You are probably looking for a change made after 478952 (known good), but no later than 478953 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
https://chromium.googlesource.com/chromium/src/+log/08012dc3513eaf24a8d44e5cd63add938ddd41e6..cc34cc148b5256fc5eb0ab46a14726be2557664d

suspect:https://chromium.googlesource.com/chromium/src/+/cc34cc148b5256fc5eb0ab46a14726be2557664d

@tommi: Could you please take a look & reassign to the right owner if it is not related to your change.


 
Actual_Print.mov
2.7 MB Download
Expected_Print.mov
1.3 MB Download

Comment 1 by tommi@chromium.org, Oct 31 2017

Labels: -Pri-1 Pri-2

Comment 2 by tommi@chromium.org, Mar 12 2018

Owner: ----
Status: Available (was: Assigned)

Comment 3 by tommi@chromium.org, Mar 12 2018

Cc: dalecur...@chromium.org
Dale - wdyt about this?
Hah, probably clipboard popup resolves any keypress as killing the clip board popup intentionally. So I think that might need to stay as a prompt() if we want print support.

I'm okay just wontfixing this too. I had no idea this is a test we did...

Sign in to add a comment