New issue
Advanced search Search tips

Issue 895787 link

Starred by 1 user
Status: Duplicate
Merged: issue 419108
Owner:
rbpotter@chromium.org
Closed: Oct 16
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug



Sign in to add a comment

[PrintPreview] 'Scale' increment/decrement button gets unresponsive while clicking on up/down arrow of it.

Reported by db...@etouch.net, Oct 16 
Chrome Version: 72.0.3582.0 Revision db5d271436f9329304e394c13ed3fb573588c2de-refs/branch-heads/3582@{#1}(32/64 bit)
OS: Windows(7,8,8.1,10) 

What steps will reproduce the problem?
(1) Launch chrome, open NTP and give 'Print' command by using Ctrl+P. 
(2) Now click on 'More settings' option to expand options then click on up/down arrow button of 'Scale'
(3) Observe scale button.

Actual: Scale increment/decrement button gets unresponsive while clicking on up/down arrow.

Expected: Scale increment/decrement button should be responsive in any ction.

This is a regression issue, broeken in 'M72', will soon update the other info:

Good Build: 72.0.3581.0
Bad Build: 72.0.3582.0
Actual_Scale.mp4
936 KB View Download

Comment 1 by db...@etouch.net, Oct 16

Labels: -Pri-1 -Type-Bug-Regression -RegressedIn-72 OS-Linux Pri-2 Type-Bug
Summary: [PrintPreview] 'Scale' increment/decrement button gets unresponsive while clicking on up/down arrow of it. (was: Regression: [PrintPreview] 'Scale' increment/decrement button gets unresponsive while clicking on up/down arrow of it.)
Correction:

Above issue is non-regression seen from 'M61' build #61.0.3113.0

Note: Issue is not seen on Mac(10.13.6,10.13.1,10.14.1) OS.

Comment 2 by rbasuvula@chromium.org, Oct 16

Status: Untriaged (was: Unconfirmed)
As per comment #1 As this being a Non-Regression issue, changing the status to Untriaged so that the issue would get addressed.

Thank You!

Comment 3 by thestig@chromium.org, Oct 16

Owner: rbpotter@chromium.org

Comment 4 by rbpotter@chromium.org, Oct 16

Mergedinto: 419108
Status: Duplicate (was: Untriaged)
This looks to me like a known Blink bug, which has been reported in Print Preview before as  https://crbug.com/763785 , that click events on the up/down buttons on number inputs are mishandled, which causes them to not respond correctly. Merging into the final Blink bug.
►

Sign in to add a comment