203138 - webclient maximizes and brings to the foreground the java application it is embedded in each time it loads a page

Status: RESOLVED EXPIRED

(Core Graveyard :: Java APIs to WebShell, defect)

Description

[Erick Epelboim]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312

When the operation of loading pages is done automatically by the program (i.e. a
web crawler program which changes the page viewed without user interaction) each
time a new page is loaded, the java application where Mozilla is embedded is
maximized (if it was previously minimized into the toolbar). Also, when a page
is loaded, the java application where the browser is embedded is brought to the
foreground. This is not noticeable for applications where page loading is
generated by user input directly (in such case it makes sense to have the
application maximized and in the foreground), but it is annoying for
applications that use the browser automatically and wish to work in the background.

Reproducible: Always

Steps to Reproduce:
1.Create a java application which embeds Mozilla using the WebClient. This
application should be able to load a page programmatically at a certain time
interval.
2.Minimize the application.
3.Try to load a page programmatically when the application is minimized (by
using a timer or a loop which loads a page at certain time intervals). 


Actual Results:  
The java application where the browser is embedded is maximized and brought to
the foreground.

Expected Results:  
Stayed minimized and not come to the foreground

I was using Java 1.4.1 and WebClient 1.3. The application is entirelly swing
based and the BrowserWindow object was placed directly over the main JFrame of
the application.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.