Regression:Content of the screenshot in feedback window is not seen properly
Reported by
adha...@etouch.net,
Jun 9 2016
|
||||||||||
Issue descriptionChrome Version:53.0.2763.0 (Official Build) dd933bda0baa6a13ab0120f0056a2b783e459efb-refs/heads/master@{#398752} (32/64-bit) OS:OS: Windows(7,8,10), Linux (14.04 LTS), Mac(10.10.5, 10.11.4) What steps will reproduce the problem? (1)Launch chrome and go to NTP or any page. (2)Now go to "Wrench" and click on "Report an issue..." overlay from help option. (3)Observe content of the screenshot in feedback window. Actual:Content of the screenshot in feedback window is not seen properly. Expected:Content of the screenshot in feedback window should be seen properly. This is a Regression issue broken in M-50. Changelog url: https://chromium.googlesource.com/chromium/src/+log/50.0.2646.0..50.0.2647.0?pretty=fuller&n=10000 Suspecting:r374648? Good build:50.0.2646.0 Bad build:50.0.2647.0 Note:Unable to provide Narrow bisect as "Report an issue..." is not available on chromium build . Kindly help to re-assign if your change is not the cause for this issue.
,
Jul 6 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 18 2016
,
Aug 9 2016
Are you still able to reproduce this issue?
,
Sep 14 2016
[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.
,
Sep 16 2016
Note:Able to reproduce the above issue on latest canary version i.e 55.0.2862.0.
,
Sep 16 2016
Just to update, issue is also reproducible on Chrome Stable# 53.0.2785.116. Using the per-revision bisect script found the below CL, https://chromium.googlesource.com/chromium/src/+log/dbac2c6af623454ae7481c683e4348cf8ca8e6fa..4745047a22b69623a37e3fece56c2c07a3398602 Issue is present on all OS, ran the bisect only on Windows as Mac and Linux does not support the revisions. Unable to find the exact suspect. Could some one please look into the issue and update. Thank You.
,
Sep 23 2016
Please re try the bisect without -o flag. adharap@ can u give a try again since per-revision cannot point single CL. Also confirm whether this is still reproducible in all channels.
,
Oct 4 2016
ran the bisect again got the same CL mentioned in comment #7. Change Log:: https://chromium.googlesource.com/chromium/src/+log/dbac2c6af623454ae7481c683e4348cf8ca8e6fa..4745047a22b69623a37e3fece56c2c07a3398602 Unable to run per-revision bisect without -o as we are getting the below error. python bisect-builds.py -a win64 -g 374556 -b 374822 Downloading list of known revisions... (use --use-local-cache to cache and re-us e the list of revisions) Traceback (most recent call last): File "bisect-builds.py", line 1433, in <module> sys.exit(main()) File "bisect-builds.py", line 1389, in main evaluator, opts.verify_range) File "bisect-builds.py", line 920, in Bisect revlist = context.GetRevList() File "bisect-builds.py", line 493, in GetRevList cache_dict_key = self.GetListingURL() File "bisect-builds.py", line 272, in GetListingURL self._listing_platform_dir + marker_param) AttributeError: 'PathContext' object has no attribute '_listing_platform_dir'. unable to check this on chromium build or script with -o as chromium doesn't support report an issue overlay. python bisect-builds.py -a win -g 374556 -b 374822. Thanks,
,
Nov 15 2016
This bug is tagged as regression.Which means that the bisects are incorrect or do not have an owner who is actively investigating. Requesting the reporter to triage and update the behavior in all the latest chrome channels and bisect if needed.Close as WontFix if not reproducible.
,
Jan 19 2017
With response to #comment 10: Above issue is not reproducible on latest chrome version i.e (57.0.2986.0),hence marking it as WontFix. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by blundell@chromium.org
, Jun 27 2016