The problem is that the final message that i see in the status bar is not from a "window.status" line in the code. It seems like beyond a certain point in the execution, the browser takes over and determines what to put in the status bar based on the jar file/something else? that its handling.
Is this true?
My requirement is to customize the final status message. So i need to figure out what exactly is happening.
What is not helping is also the fact that the loading process is so fast that i cannot see any of the intermediary messages. Is there any way to slow down the applet loading process, other than to try over a very slow connection?
The browser uses the status bar for its own purposes. While the applet can use it, too, I wouldn't expect those messages to be visible for very long, as they may be replaced by the browser at any time.
But more importantly, the status bar is not very prominent to the user. If the applet needs to provide feedback, it should do that in the applet GUI (where there's no interference by the browser).
I agree to your point, but the issue here is very specific.
The browser is ofcos getting the final say in what gets displayed in the status bar. The problem is that what it is displaying is something that I don't want to be there. So i need to wrest control from the browser and display my custom string as the final one in the status bar.