Chrome Version: 71.0.3554.0 (Official Build) Revision	50b24262ba0c4e14c723112f9aad3686dc6462c1-refs/branch-heads/3554@{#1} (32/64-bit)
OS: Windows(7,8,8.1,10), Mac(10.12.6, 10.13.1, 10.13.6, 10.14) and Linux(14.04 LTs).

What steps will reproduce the problem?
1. Launch Chrome and give print command on any webpage.
2. Type any keyword in 'Pages' text-box so that 'Invalid page range' error message appears.
3. Select 'All' radio button under pages section ('Invalid page range' error message will disappear).
3. Now again click in 'Pages' text-box and observe.

Actual: 'Invalid page range' error message doesn't appear.
Expected: 'Invalid page range' error message should appear.

This is a regression issue, broken in M-71 series, below is manual regression range.

Good build: 71.0.3551.0 (Revision: 590851)
Bad build: 71.0.3552.2 (Revision: 591210)

Using the 'per-revision' script providing the bisect result:

You are probably looking for a change made after 591108 (known good), but no later than 591109 (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/974aa7b559b4361d7410479796becb0b933dc6a4..e73e92b7fbf4206ffdb20282ac73bcbed7cf910e

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

@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.

Kindly review the attached screen-cast for reference.

Thank you.
 

Deleted: Actual behavior.mp4 799 KB

	Actual behavior.mp4 799 KB View Download

Deleted: Expected behavior.mp4 494 KB

	Expected behavior.mp4 494 KB View Download