New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 896580 link

Starred by 4 users
Status: Fixed
Owner:
rbpotter@chromium.org
Closed: Oct 31
Cc:
█ manoranj...@chromium.org
nyerramilli@chromium.org
pbomm...@chromium.org
rbasuvula@chromium.org
dpa...@chromium.org
█ xlou@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression

Blocked on:
issue 879261
Blocking:
issue 896748



Sign in to add a comment

Regression: Print Preview number control arrow buttons/arrow keys are broken

Reported by pranjali...@etouch.net, Oct 18 
Chrome Version: 72.0.3584.0 (Official Build) 945ab041ec6ac3fb389f94dcbfebb1839a12a69b-refs/branch-heads/3584@{#1}(32/64 bit)

OS:  Win(7,8,8.1,10).

What steps will reproduce the problem?
1.Launch chrome and give print command.
2.Now click on copies spinner and observe.

Actual  : Collate checkbox is not seen on print preview after increasing number of copies.
Expected: Collate checkbox should be seen on print preview after increasing number of copies.

This is Regression issue seen in M-72, and will soon update other info.
Good Build: 72.0.3583.0
Bad Build: 72.0.3584.0
Actual Result.mp4
277 KB View Download
Expected Result.mp4
247 KB View Download

Comment 1 by pranjali...@etouch.net, Oct 18

Labels: hasbisect OS-Linux OS-Mac
Owner: xlou@chromium.org
Status: Assigned (was: Unconfirmed)
Unable to provide 'per-revision' bisect as it shows "We don't have enough builds to bisect . revlist: []" error message,Hence provided suspect through 'Chromium bisect'

Chromium bisect URL:
https://chromium.googlesource.com/chromium/src/+log/7e3361f0a1f2962a85c8cf36b6ea2f403328419e..177774d57a744b75630cba5507c3bf1ed419aea3	

Suspect: https://chromium.googlesource.com/chromium/src/+/62f2f8f209a82db0dd5a311eb4f844bddb75c98e

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

Thank You

Comment 2 by rbasuvula@chromium.org, Oct 18

Labels: ReleaseBlock-Stable
As this is a recent regression adding release blocker label for this issue.Please reduce priority or remove if not the case.

Thank You!

Comment 3 by rbasuvula@chromium.org, Oct 18

Cc: pbomm...@chromium.org

Comment 4 by rbpotter@chromium.org, Oct 18

Cc: -pbomm...@chromium.org xlou@chromium.org
Owner: rbpotter@chromium.org
Pretty sure the culprit is the Polymer 2 change, not N-up. Will confirm later today.

Comment 5 by rbpotter@chromium.org, Oct 18

Cc: pbomm...@chromium.org

Comment 6 by xlou@chromium.org, Oct 18 

Thanks, Rebekah.

Comment 7 by rbpotter@chromium.org, Oct 18

Blocking: 896748

Comment 8 by rbpotter@chromium.org, Oct 18

Blockedon: 879261
Confirmed that this is due to the Polymer 2 change, and is due to a previously reported Blink bug with number inputs. The collate checkbox appears correctly if you type a new copies value, instead of using the up/down buttons (or the keyboard arrow keys).

Comment 9 by rbpotter@chromium.org, Oct 19 

 Issue 897034  has been merged into this issue.

Comment 10 by rbpotter@chromium.org, Oct 22

Summary: Regression: Print Preview number control arrow buttons/arrow keys are broken (was: Regression:Collate checkbox is not seen on print preview.)

Comment 11 by rbasuvula@chromium.org, Oct 24 

Friendly ping! Could you please provide any update on this issue as it has been marked as a stable blocker.

Thank You!

Comment 12 by dpa...@chromium.org, Oct 25

Cc: dpa...@chromium.org manoranj...@chromium.org
 Issue 898770  has been merged into this issue.

Comment 13 by dpa...@chromium.org, Oct 27

Status: Started (was: Assigned)
Candidate fix is at https://chromium-review.googlesource.com/c/chromium/src/+/1211669. Waiting for reviewer feedback.

Comment 14 by rbasuvula@google.com, Oct 31 

Gentle ping! Could you please provide any update on this issue as it has been marked as a stable blocker.

Thank You!

Comment 15 by dpa...@chromium.org, Oct 31 

@rbpotter: Can we mark this as fixed now, or is there anything else to be done here?

Comment 16 by rbpotter@chromium.org, Oct 31

Status: Fixed (was: Started)
Tested and this is fixed on ToT (see https://crrev.com/c/1211669).
►

Sign in to add a comment