This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I'm not that familiar with Firefox, but I was asked to look at an issue with Firefox for the application I am working on. It seems that once a user displays some pages in the application, clicking on a link in the page will display not only the requested page but also pop up a new window containing the message: Error 404 Servlet Not Found [object Event].
This is an issue in Firefox 184.108.40.206 and Netscape 9 only. IE 6 SP2 and Opera 9.23 do not have the problem. I have monitored the HTTP requests in IE using HTTP Watch and in Firefox using Live HTTP Headers. In Firefox, I see additional requests similar to:
The only ideas I have at this point are 1) it's a Firefox/Mozilla security setting issue or 2) it's problem with the HTTP server (we are using Microsoft-IIS/5.0 as the front-end HTTP server for WebSphere 5).
I'm not sure this is the proper forum but I'm desperate for ideas.
Originally posted by Jay Damon: I don't really see a problem with that anchor tag other than it does not contain and end tag.
Well, that is a big problem. Malformed HTML is almost guaranteed to cause issues. Without a closing tag, how does the browser know where the link stops?
If all you are trying to do is to execute some JS, why have a link at all? Use an appropriately styled <span> with an onclick handler. That way you avoid unintended semantic actions.
However, after reviewing the code once again, I have discovered there are TWO functions named "openwindow"
Joined: Jul 31, 2001
Thanks for the response. However, you're preaching to the choir. The application I am working on is over 10 years old. To give you some perspective, I've seen references in the code to Internet Explorer 2. Heck, I didn't even know there was an IE 2.
Thanks again for your help though. I think I may finally be on the road to a solution.
Originally posted by Jay Damon: there is always the inevitable resistance to changing "what works."
Well, in this case you have a pretty strong argument for "not working". At least part of the fix is to eliminate the sloppy code. They can't argue with that. (Well, I guess they could, but not reasonably).