Closed Bug 923389 Opened 11 years ago Closed 2 years ago

Focus does not back on web page after printing from FireFox PrintDialog.

Categories

(Core :: DOM: Core & HTML, defect, P5)

24 Branch
x86_64
Windows 7
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: synelnyk, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)

Steps to reproduce:

I need to print some control content from web page using default PrintDialog of browser. 
 function doPrint() {
                var printFrame = document.getElementById("reportout").contentWindow;
                printFrame.print();
                txbxCtrl.Focus();
            }
Sush simple script work fine in IE but wrong in FireFox. I use 24.0 FireFox version.


Actual results:

After PrintDialog showed and user pressed Print button, the web page focus, and user need to press TAB button from 9 to 15 times for return focus on page content.



Expected results:

Focus should be back on previous active control after printing.
Severity: normal → major
Component: Untriaged → Web Apps
Priority: -- → P5
This isn't related to web apps.
Component: Web Apps → Untriaged
Thanks.
What is this related to? And who to turn to with this problem? This is simple javascript, and FireFox performs it with problem of focus.
(In reply to Jason Smith [:jsmith] from comment #1)
> This isn't related to web apps.

 Who to turn to with this problem? This is simple javascript, and FireFox performs it with problem of focus.
Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
Please post the actual testcase here?  It's hard to say what it's trying to do based on the info in comment 0 (e.g., what's "txbxCtrl"?)
Flags: needinfo?(synelnyk)
QA Whiteboard: qa-not-actionable

Should the issue still occur, feel free to reopen this. A clear STR or more clarification for comment 4 is a huge help to make this actionable. Thanks.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.