New issue
Advanced search Search tips

Issue 900110 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Regression : [Print Preview] Error message is not seen for invalid input in 'Custom' text field.

Reported by avsha...@etouch.net, Oct 30

Issue description

Chrome Version : 72.0.3595.2 (Official Build) 4af8b5a14fa87ad1e81fa9ae20c30f9a8c1494cb-refs/branch-heads/3595@{#4} 32/64 bit
OS : Mac(10.13.1, 10.13.6, 10.14.1), Windows(7,8,10), Linux(14.04 LTS)

What steps will reproduce the problem?
1. Launch chrome, navigate to chrome://flags page and open Print Preview window.
2. Select 'Custom' radio button and type "1" in text field.
3. Now hit 'Spacebar' key multiple times and observe 'Custom' text field.

Actual Result : Error message is not seen for invalid input (Ex. "1   ") in 'Custom' text field.

Expected Result : Error message should appear for 'Custom' field when user enters any valid number followed by multiple spaces.

This is a regression issue broken in M-71 and below is the bisect information:
Good Build : 71.0.3558.0 (Revision : 593043)
Bad Build : 71.0.3559.0 (Revision : 593399)

Chromium bisect URL:
https://chromium.googlesource.com/chromium/src/+log/ca9042e14b381271ea4be6e3a6c1c3920d9dd37d..21eea353daea69d467fbe830aa9cc7aee0fa6cf3

Suspecting : r593394 ?

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:
1. Able to reproduce issue in Canary #72.0.3595.0, Beta #71.0.3578.27
2. Unable to provide bisect using 'per-revision' script as it shows "We don't have enough builds.." error message for above regression range, hence provided suspect through 'Chromium bisect'. (Tried on other machines but still getting the same error)

Thank you..!
 
Actual_Result_1.mov
6.8 MB View Download
Expected_Result_1.mov
6.9 MB View Download
Status: WontFix (was: Assigned)
The old Print Preview UI has worked this way for a very long time, and as long as an error shows up if the user types something after the spaces (e.g. "1   2" or "1   a"), I don't think it matters if we allow some extra whitespace after the number. WontFix.

Sign in to add a comment