Regression: Print preview page of chrome://accessability is not seen properly.
Reported by
rk...@etouch.net,
Apr 28 2016
|
|||||||
Issue descriptionChrome Version: 52.0.2719.0 Revision db7757b63f29696b9b465949f9704a0d9d149f2b-refs/heads/master@{#390251}(32/64 bit) OS: Mac OS X(10.10.5, 10.11.4), Windows (7,8,8.1,10),Linux (14.04 LTS) What steps will reproduce the problem? (1) Launch chrome, go to chrome://accessibility/, for accessibility entry click on 'accessibility off' link button. (2) Now click on 'show accessibility tree' link, then click on 'hide accessibility tree' link. (3) Press ctrl+p and observe the preview page. Print preview page of chrome://accessability is not seen properly. Print preview page of chrome://accessability should seen properly. This is a regression issue,broken in 'M-51', below is bisect info: Good Build: 51.0.2680.0 Bad Build: 51.0.2681.0 Narrow Bisect: https://chromium.googlesource.com/chromium/src/+log/6b03d171d4137691637129ebad5cab20f4babbbb..7288268a683040968054a3dcfedef28d9151bc1d?pretty=fuller&n=100 Suspecting: r381560
,
May 2 2016
Verified the issue on Latest Canary# 52.0.2272.0 on Windows, Mac and Linux and still able to reproduce the issue. Followed the below steps, (i) Navigate to chrome://accessibility (ii) In accessibility, click on accessibility on and click on show accessibility tree and click on Ctrl + P and observe. Thank You.
,
May 2 2016
chrome://accessibility is a rarely used page. It is primarily known to developers who work on the Chrome Accessibility team. I know of no instance when it was necessary to print this page. Definitly this issue should be fixed, but I believe that it should not be block stable.
,
Nov 14 2016
@dmazzoni, would you mind taking this bug on?
,
Nov 15 2016
,
Jun 26 2017
This page seems to look quite different in Chrome 58 (stable) and 61 (canary). Is this still an issue? Also, printing this page is not a priority, so marking P3.
,
Jul 27 2017
,
Aug 17 2017
Closing due to lack of feedback, and since the page looks very different from the video. If this was the same issue as 650216 the underlying problem may also have been resolved as of M60. Please comment if this is still an issue in 60+. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by tkonch...@chromium.org
, Apr 28 2016