Under Destination, network printer names show as UNC path
Categories
(Core :: Printing: Setup, enhancement)
Tracking
()
People
(Reporter: jscher2000, Unassigned)
Details
Attachments
(2 files)
Example of too-long UNC paths from SUMO
On the Print Setup side of the combined Print Preview/Setup overlay, the Destinations drop-down lists networked printers under a UNC path rather than by their name as known in Windows. As an example of the difference:
UNC path: \\PrintServices\HP Duplex
Windows: HP Duplex on PrintServices
|
||
Updated•2 years ago
|
|
Reporter | |
Comment 1•2 years ago
|
||
Could we reclass this as a defect? The printer list is unusable with long paths, as shown in this SUMO thread: https://support.mozilla.org/questions/1380189
|
||
Comment 2•2 years ago
•
|
||
Excellent find Jscher! I'm gonna try to get some more eyes on this. Maybe someone can help me escalate it so that it can get prioritized because it looks like this new naming behavior is more confusing than it was before.
I was wondering do you think you'd be able to narrow down the regression range using Nightly builds? I know that usually helps the devs respond faster when they know the date of the build the behavior changed or regressed. They can pinpoint the changeset that caused it.
Most people recommend https://mozilla.github.io/mozregression/quickstart.html (which I'm sure you know of) which automates the process of downloading and opening nightly builds from various dates (in new, clean profiles) and asking you whether the bug exists in them.
I usually opt to do it manually [which can be time consuming] but I have better control of everything that's happening. If you go the manual route, I usually grab the builds from the 1st, 15th & 30th/31st of the month from here: https://archive.mozilla.org/pub/firefox/nightly/
Then I make notes of which builds it's working in or broken in then keep narrowing it down within that 2 week range by working my way backwards 5 days at a time. Ex. July 1st - Works, July 15th - Broken. I test July 10th next. Bisecting as best as I can.
|
|
Reporter | |
Comment 3•2 years ago
|
||
Hi Noah, I have used Mozregression many times, but our security software is very unhappy with the small intermediate builds so it's become difficult on this computer (numerous modal dialogs, reports to IT...). I need to update an old personal one at some point.
Hi, I tested it like Noah said.
Index of /pub/firefox/nightly/2022/01/2022-01-17-03-58-08-mozilla-central-l10n/ work
Index of /pub/firefox/nightly/2022/01/2022-01-17-21-49-41-mozilla-central-l10n/ problem
2022-01-18-09-50-36-mozilla-central-l10n/ problem
Index of /pub/firefox/nightly/2022/01/2022-01-17-21-49-41-mozilla-central-l10n/ problem
Index of /pub/firefox/nightly/2022/01/2022-01-19-09-34-35-mozilla-central-l10n/ problem
I chose this installation firefox_version.pl.win64.installer.exe .
Description
•