Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350650 - focus after print from IE8 browser not returned to application
Summary: focus after print from IE8 browser not returned to application
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-29 01:53 EDT by Michael Hoppe CLA
Modified: 2019-11-27 07:11 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Hoppe CLA 2011-06-29 01:53:50 EDT
Build Identifier: M20090211-1700

When I open a print dialog via javascript on a html document shown in the embedded browser widget of my rcp application and confirm that print dialog with ok or cancel the focus does not return to my rcp application, as soon there is another IE8 window or the eclipse workbench open.

Reproducible: Always

Steps to Reproduce:
1. Open an IE8 window or the eclipse workbench
2. In a rcp application with embedded swt browser: open a HTML document which can open the print dialog
3. Open the print dialog
4. Close the print dialog with ok or cancel
5. the focus does not go back to the rcp application but to the other IE8 window or the eclipse workbench window
Comment 1 Darryl Lyons CLA 2011-08-21 19:58:15 EDT
I've got a very similar problem. When I call the javascript print() function and either press OK or CANCEL in the print dialog, the last used application comes into focus.

E.g. If I had Micrsoft Word open, and then go to our RCP Application and print the html document present in the embedded SWT Browser, Micrsoft Word comes into focus.
Comment 2 Lars Vogel CLA 2019-11-27 07:11:06 EST
This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.