Status Update
Comments
dt...@chromium.org <dt...@chromium.org> #2
[Empty comment from Monorail migration]
[Monorail components: Internals>Printing]
[Monorail components: Internals>Printing]
aw...@chromium.org <aw...@chromium.org> #3
@Reporter:
1. Can you please specify which version of Chrome you are seeing this with?
2. What do you normally have for the margins of your receipt printer? (E.g., "None"? "Default"?)
1. Can you please specify which version of Chrome you are seeing this with?
2. What do you normally have for the margins of your receipt printer? (E.g., "None"? "Default"?)
ph...@chromium.org <ph...@chromium.org> #4
[Empty comment from Monorail migration]
mo...@blox.ae <mo...@blox.ae> #5
1.Version 89.0.4389.82 (Official Build) (64-bit)
2.I mentioning margin as "Default", but i am changing Scale option every time. while selecting Receipt printer and barcode printer. i need it should not be changed while i am selecting barcode printer and receipt printer from chrome.
2.I mentioning margin as "Default", but i am changing Scale option every time. while selecting Receipt printer and barcode printer. i need it should not be changed while i am selecting barcode printer and receipt printer from chrome.
[Deleted User] <[Deleted User]> #6
Thank you for providing more feedback. Adding the requester to the cc list.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
For more details visit
ph...@chromium.org <ph...@chromium.org> #7
As per https://crbug.com/chromium/1186601#c0 , it seems to be a feature request hence marking it untriaged and requesting someone from dev to look into it.
Thanks.!
Thanks.!
dh...@chromium.org <dh...@chromium.org> #8
[Empty comment from Monorail migration]
aw...@chromium.org <aw...@chromium.org> #9
Margins and scale factor are sticky settings, so chosen values persist on different destination selections. These settings are not saved per-destination, so if you change one manually then you would need to revert that when switching back to a different destination. That is WAI.
It sounds like you're asking about the possibility for sticky settings to be per-destination, where a change made to one doesn't automatically apply to a different destination. Is that correct? This would be a pretty non-trivial change to the UX behavior, and could easily break many other users' workflows.
It sounds like you're asking about the possibility for sticky settings to be per-destination, where a change made to one doesn't automatically apply to a different destination. Is that correct? This would be a pretty non-trivial change to the UX behavior, and could easily break many other users' workflows.
ni...@chromium.org <ni...@chromium.org> #10
[Empty comment from Monorail migration]
km...@chromium.org <km...@chromium.org> #11
From our feature triage meeting:
1. Since this impacts Print Preview, we'd like to get rbpotter@'s input.
2. We were discussing two options:
a. Persist presets per device (being careful to clean up old settings)
b. Offer customizable presets (similar to macOS's system dialog)
[Monorail components: UI>Browser>PrintPreview]
1. Since this impacts Print Preview, we'd like to get rbpotter@'s input.
2. We were discussing two options:
a. Persist presets per device (being careful to clean up old settings)
b. Offer customizable presets (similar to macOS's system dialog)
[Monorail components: UI>Browser>PrintPreview]
[Deleted User] <[Deleted User]> #12
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 visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
km...@chromium.org <km...@chromium.org> #13
Re: https://crbug.com/chromium/1186601#c10 , I think we still need to collect rbpotter@'s input.
km...@chromium.org <km...@chromium.org> #14
[Empty comment from Monorail migration]
aw...@chromium.org <aw...@chromium.org> #15
Improving upon this is still a desired end-goal. The items mentioned in https://crbug.com/chromium/1186601#c10 are still applicable.
km...@chromium.org <km...@chromium.org> #16
I don't think we still need the user's feedback to evaluate this request.
th...@chromium.org <th...@chromium.org> #18
aw...@chromium.org <aw...@chromium.org> #19
I think you're right! Sorry -- I expect this should be resolved by https://crbug.com/chromium/1295921 .
ha...@google.com <ha...@google.com> #20
[Empty comment from Monorail migration]
is...@google.com <is...@google.com> #21
This issue was migrated from crbug.com/chromium/1186601?no_tracker_redirect=1
[Multiple monorail components: Internals>Printing, UI>Browser>PrintPreview]
[Monorail blocked-on:crbug.com/chromium/1295921 ]
[Monorail mergedinto:crbug.com/chromium/1295921 ]
[Monorail components added to Component Tags custom field.]
[Multiple monorail components: Internals>Printing, UI>Browser>PrintPreview]
[Monorail blocked-on:
[Monorail mergedinto:
[Monorail components added to Component Tags custom field.]
Description