Non Regression: Error message is not displaying for negative boundary values of print preview |
||||||
Issue descriptionChrome Version: 58.0.3000.0 Dev OS: Ubuntu 14.04,Windows What steps will reproduce the problem? (1)Launch chrome and naviagate to the url: https://en.wikipedia.org/wiki/Main_Page (2)ctrl+p print preview opens and enter-1 in the left side pages section of the print preview page and observe. Note:Negative range is below 0(-1 to till the negative page range) Expected Result:Error should be displayed for the negative series of pages. Actual Result:Error is not displaying for the negative series of pages. This is a Non-regression issue as same is seen from M-40 series.
,
Feb 2 2017
Looks like -X is interpreted as print from the beginning to page X (that is what previews and prints if you do this). Looking at the comments in print_preview_utils.js this is likely intentional. It definitely looks a little odd since it appears to be a negative number, but we also support X- as meaning page X to the end and - as meaning the entire document, so -X meaning pages 1-X makes sense in that context. CC jawag@ for input on whether this is something we would want to change.
,
Feb 11 2017
rbpotter@ your explanation in #2 makes sense, but I have a hard time imagining that very many users would know that typing "-X" would cause pages 1-X to be printed. Especially given that the example that is shown inside the box indicates that you should type "1-X" in order to print pages 1-X. It seems like in most cases negative numbers would just be the result of typos, in which case the current functionality could actually be quite confusing; say the user intended to print page X of a 10 page document and accidentally typed "-X", they would get pages 1-X instead of page X. Unless there is some legitimate use case that I'm missing, I think that returning an error for negative numbers sounds reasonable.
,
Mar 28 2017
It does look weird.
,
Apr 6 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 10 2018
... but it's a minor and users can look at the preview to figure out "-1" means "1-1". |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by durga.behera@chromium.org
, Feb 2 2017Status: Untriaged (was: Unconfirmed)