Issue metadata
Sign in to add a comment
|
Advanced printer options not saved |
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Steps to reproduce the problem: 1. Open a PDF line this: https://arxiv.org/pdf/1712.06148.pdf 2. Print and choose a cloud printter 3. Go to more settings / advanced / Change printer options... 4. Change staple from 'Off' to 'Top left' (I assume any option would work, but staple is one I use) 5. Push Print 6. Repeat steps 1-3 What is the expected behavior? Staple remembers it's last state of "Top left" Note that these options used to be rememberd. It was sometime in the last 6-8 weeks that the options were removed. What went wrong? "Staple" has reverted to "Off" Did this work before? Yes not sure, sometime in the last few months Chrome version: 63.0.3239.132 Channel: n/a OS Version: Flash Version:
,
Jan 26 2018
,
Jan 29 2018
,
Jan 29 2018
Able to reproduce the issue on Windows 10, Debian Rodete, Mac 10.13.2 with Chrome #63.0.3239.132, but not with latest stable #64.0.3282.119, Beta #64.0.3282.119, Dev #65.0.3325.18, Canary #66.0.3334.0 pfr@ Could you please update chrome to the latest version and let us know your observations.
,
Jan 30 2018
,
Feb 1 2018
Confirmed that it is working on 64.0.3282.119 thanks
,
Feb 2 2018
As per comment #6, Closing this issue.
,
Feb 9 2018
Thanks for reporting and checking the bug got fixed.
,
Feb 10 2018
Why is that issue view restricted, since it is not a security issue or anything? (Don't read this if you don't want to, but Chromium is really 100% Google and no one outside can access.)
,
Feb 10 2018
re: comment 9 - By default, this bug tracker restricts bugs filed by @google.com accounts to be viewable by @google.com accounts only. The first instance of this bug was filed by someone with an @google.com account, so all the other duplicates got merged into this one. Since you asked, there is nothing really confidential about bug 796900 , I will happily remove the restriction.
,
Feb 10 2018
That's weird; I've seen several bugs filed by @google.com accounts that are publicly visible and have no comments (so it's not like anyone lifted the view restriction later on).
,
Feb 10 2018
This bug was filed by a @google.com account as well, and it doesn't look like it was ever view restricted.
,
Feb 10 2018
re: comment 11 - Ya, I noticed too. I don't know for sure, but I think folks with @google.com accounts can decide to override the default and make the bugs they file public. Please consider continuing to discuss this topic on the chromium-discuss mailing list, rather than this bug. As we are going off-topic here. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pfr@google.com
, Jan 26 2018