Regression: 'Add another' drop down is seen after dragging horizontal handle of tracing window to extreme upward.
Reported by
jshan...@etouch.net,
May 19 2016
|
||||||||
Issue descriptionChrome Version: 52.0.2741.0 (Official Build) 19d105a2a1ec66924ff415f27ff170db7a67ba36-refs/heads/master@{#394609} 32/64-bit. OS: Windows(7,8,10), Mac (10.10.5)(10.11.4), Linux(Ubuntu 14.04 LTS) Steps: 1. Launch Chrome and navigate to chrome://tracing. 2. Click on Record button, complete the recording and click on 'File Size Stats'. 3. Drag the horizontal handle of tracing window upwards and observe. Actual:'Add another' drop down is seen even after dragging horizontal handle of tracing window to extreme upward. Expected:'Add another' drop down should not be seen after dragging horizontal handle of tracing window to extreme upward. This is a regression issue broken in M-50, below is bisect info. Good build: 50.0.2631.0 Bad build: 50.0.2633.0 Narrow bisect: https://chromium.googlesource.com/chromium/src/+log/08898ba307a784f14964995b3d820761d2059359..acce4131402e62abdee469c445849c1036357e6e?pretty=fuller&n=100 Suspecting: r371756 ? Please help to re-assign if your change is not the cause for this issue.
,
May 19 2016
Hmm it seems quite unlikely that the CL in question was the cause, though you never know :) Could we redo the bisect? dsinclair: does this look like a problem with the html/css of about:tracing (as opposed to a renderer issue?)
,
May 19 2016
,
May 19 2016
Tracing bugs aren't release-block as it's a chromium developer tool.
,
May 20 2016
@dsinclari: Thanks, I'll keep that in mind while triaging tracing bugs.
,
May 20 2016
With response to comment #2, re-bisected again on different machine and got the same range as given above. Suspecting: r371759 ? Please help to re-assign if your change is not the cause for this issue.
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 20 2016
Just to update above issue is fixed in latest canary version 53.0.2773.0
,
Jul 9 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 18 2016
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ashej...@chromium.org
, May 19 2016