User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Implement the NewWindow3 event to the API because: a) Newer apps that have already implemented this and use it need to be able to switch to Mozilla. b) This event provides more info than the NewWindow2 event and is easier to write envent handlers for it that open new windows with the requested URL without implementing an internal browser in the control (see bug 142904 @ https://bugzilla.mozilla.org/show_bug.cgi?id=142904) Reproducible: Always Steps to Reproduce: 1. Write event handler like the following: Private Sub object_NewWindow3(ppDisp,Cancel,dwFlags,bstrUrlContext,bstrUrl) MsgBox "Navigating from:"+bstrUrlContext+vbCrLF+_ "Navigating to:"+bstrUrl End Sub 2. Launch any link that looks like <a href="http://www.mozilla.org" target="_blank">Go to mozilla.org in a new window</a> Actual Results: Nothing happens. the NewWindow3 event is not fired Expected Results: NewWindow3 event should fire causing the above sub to create a MsgBox with the navigation information This bug is sort of an enhancement, but it is a required enhancement. Without this some developers will not be able to switch to the Mozill ActiveX control. For this reason: setting to blocker. If this is inappropriate please switch to a more approrpiate severity level.
What severity should it be? Setting to enhancement.
Changing severity to major. Didn't notice it was changed to major until I checked my e-mail. Don't ask me how I 'didn't notice' I don't know. Sorry.
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/
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.