New issue
Advanced search Search tips

Issue 885112 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug



Sign in to add a comment

[Print]Error message for invalid page number is not displayed

Reported by vineetha...@etouch.net, Sep 18

Issue description

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) and Linux(14.04)

What steps will reproduce the problem?
(1) Launch Chrome open NTP and give print command using 'Ctrl+P' to open Print Preview overlay.
(2) Click on second textbox field under Pages and enter continuous invalid page number.
(3) Immediately press tab to navigate focus to the next available element on print preview overlay and observe.

Actual  : Error message for invalid page number is not displayed before pressing tab.
Expected: Error message for invalid page number should be displayed before pressing tab.
          
This is a non-regression issue, seen from M67 as new Print Preview UI has been introduced from M67 series.

Note: 
1.Require to enable 'Enable new Print Preview UI' flag under chrome://flags for builds before #71.0.3552.2
2.Issue is not seen on Mac OS. 

Thank you.
 
ActualVideo.mp4
402 KB View Download
Status: Untriaged (was: Unconfirmed)
As this being a Non-Regression issue, changing the status to Untriaged so that the issue would get addressed.

Thank You!
Cc: rbpotter@chromium.org
Owner: rbpotter@chromium.org
This doesn't seem to reproduce for me on Canary (71.0.3562.1), but we did experiment with a dropdown on today's Canary. I'll try again tomorrow when we go back to radio buttons.
Status: WontFix (was: Untriaged)
Radio buttons are back on current Canary, so double checked to see if this reproduces. Still does not seem to still be an issue; the error message shows up in Canary 71.0.3563.0 as soon as tab is pressed and the other settings are disabled. That it doesn't immediately show up on keypress is expected as we wait to process user input until after there is a pause, rather than trying to process after each key event, which can freeze the UI and annoy the user.

Sign in to add a comment