New issue
Advanced search Search tips

Issue 866817 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jul 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: [Print Preview] All the preview options gets disabled for invalid page range.

Reported by dchau...@etouch.net, Jul 24

Issue description

Chrome Version: 68.0.3440.75 (Official Build) Revision	cf598d63a4f1b9e7cd14f2a8433276b196e3e07d-refs/branch-heads/3440@{#738} 32/64-bit.
OS: Win(7,8,8.1,10) ,Mac(10.12.6 , 10.13.1 , 10.13.6, 10.14)  and Linux(14.04 LTS).

Pre-condition: Enable 'Enable new Print Preview UI' flag from chrome://flags

What steps will reproduce the problem?
1. Launch Chrome and give print command on any webpage.
2. Type any invalid page range in 'Pages' text-box and observe.

Actual: All the preview options gets disabled on typing invalid page range in 'Pages' text-box.
Expected: Only 'Print' button should get disabled on typing invalid page range in 'Pages' text-box.

This is a regression issue, broken in M-66 series, below is manual regression range:

Good build: 66.0.3345.0 (Revision: 536027)
Bad build: 66.0.3346.0 (Revision: 536238)

Using the per-revision bisect providing the bisect results:

You are probably looking for a change made after 536228 (known good), but no later than 536229 (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/5a5241642a8e0259ed9c7a847d63a436ce175ca7..a1d5b83fb1a536497e67a65decaaa12ca3036f21

Suspecting: https://chromium.googlesource.com/chromium/src/+/a1d5b83fb1a536497e67a65decaaa12ca3036f21

@rbpotter : Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

NOTE: This issue is also reproducible on Stable #67.0.3396.99, Beta #68.0.3440.68, Dev #69.0.3493.3 and Canary #70.0.3501.0

Kindly review the attached screen-cast for reference.

Thank you.
 
Actual behavior.mp4
1.0 MB View Download
Expected behavior.mp4
1.0 MB View Download
Status: WontFix (was: Assigned)
This is an intentional change. The desired behavior is that only the pages input remains enabled so that the user can correct the error. This prevents the user from getting into a state with multiple errors on the page. Closing this as it seems to be working as intended, feel free to re-open if the pages input is getting disabled (this was not the case when I tested on Chrome Dev).

Sign in to add a comment