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

UNCONFIRMED
Unassigned

Status

()

Core
DOM: Core & HTML
P5
major
UNCONFIRMED
4 years ago
4 years ago

People

(Reporter: Alexandra, Unassigned, NeedInfo)

Tracking

24 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
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.
(Reporter)

Updated

4 years ago
Severity: normal → major
Component: Untriaged → Web Apps
Priority: -- → P5
This isn't related to web apps.
Component: Web Apps → Untriaged
(Reporter)

Comment 2

4 years ago
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.
(Reporter)

Comment 3

4 years ago
(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.

Updated

4 years ago
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)
You need to log in before you can comment on or make changes to this bug.