If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

installing a printer inside the print dialog caused a long script warning which caused a ui deadlock of sorts

UNCONFIRMED
Unassigned

Status

()

Core
Printing: Setup
UNCONFIRMED
4 years ago
3 years ago

People

(Reporter: will.o.west, Unassigned)

Tracking

23 Branch
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 808349 [details]
Screen Shot 2013-09-22 at 6.27.39 PM.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130814063812

Steps to reproduce:

pre:
OSX 10.8
no printers installed / configured
have network autodiscover printer available
printer that requires a decent amount of time to download / install

1. print a page (this was a popup / separate window / invoice thingy)
2. in dialog select discovered printer
3. click thru install dialogs, perhaps distractedly waiting around in between
4. await download/install process
5. attempt to use printer by clicking "print"



Actual results:

a) "print" button is blue but vaguely pulsing
b) unresponsive script warning for preference dialog (internal js, NOT page js) is on the page that we attempted to print
c) could not click print (or cancel, or PDF, etc), seemingly because of the script warning
d) could not click stop / continue because the modal print dialog out-modal'ed the top-toast modal
e) interestingly, the combo boxes for printer / quality selection still worked


Expected results:

a) clicking print after installing the printer should have worked

b) OR the script dialog should have greater modal priority, since it appeared second and needed to be addressed before the print dialog could be used

Updated

3 years ago
Component: Untriaged → Printing: Setup
Product: Firefox → Core
You need to log in before you can comment on or make changes to this bug.