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

Issue 608316 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression:Ruler is not displayed properly after giving print command in Chrome://tracing

Reported by adha...@etouch.net, May 2 2016

Issue description

Chrome Version:52.0.2722.0 (Official Build) 884d81a6495cd1138a77425df55d80030b768de1-refs/heads/master@{#390853}(32/64-bit)
OS:OS: Windows (7,8,8.1), Mac OS X 10.11.14, Linux (14.04 LTS)

What steps will reproduce the problem?
(1)Launch chrome, go to chrome://tracing page and click on 'Record' button.
(2)Give print command(Ctr+P) and observe.

Actual:Ruler is not displayed properly after giving print command

Expected:Ruler should be displayed properly after giving print command

This is a Regression issue broken in M-44,below is the Narrow bisect info:
https://chromium.googlesource.com/chromium/src/+log/e935f62821ae59f147546be18ffdc336d683ea55..d15048d49fee7167c57825bba4d899a7effcad3a?pretty=fuller&n=100

Suspecting:r326501?

Good build:44.0.2381.0
Bad build:44.0.2383.0

Kindly help to re-assign if your change is not the cause for the issue.


 
Actual.mp4
705 KB Download
Expected.mp4
508 KB Download
Owner: ----
Status: Untriaged (was: Assigned)
I don't see how my change might have caused this, changing the status to untriaged.
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 11 2016

Labels: -M-53 -Pri-1 M-54 MovedFrom-53 Pri-2
This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
Are you still able to reproduce ? If not please mark as Wont'Fix or re-bisect if needed.
Labels: Needs-Bisect
[Bulk Edit]- Assigning to In house-HYD Team and apply label - hasbisect-per-revison

If the issue still persist, try bisecting again with per-revision bisect script.

Comment 6 by adha...@etouch.net, Sep 16 2016

Labels: -Needs-Feedback
Note:Able to reproduce the above issue on latest canary version i.e 55.0.2862.0.

Status: WontFix (was: Untriaged)
marking as Wont fix, as this is out of scope as per chrome://tracing test plan

Sign in to add a comment