Closed Bug 303829 Opened 20 years ago Closed 14 years ago

The mozilla activex control doesn't fire the DISPID_WINDOWCLOSING event when window.close is called

Categories

(Core Graveyard :: Embedding: ActiveX Wrapper, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: fret, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 If you attach a DWebBrowserEvents2 event sink to the mozilla activex control you can receive DISPID_NEWWINDOW2 events but you don't get the corrasponding DISPID_WINDOWCLOSING event to allow you to close the new window. In fact you get no event at all when window.close is called in the javascript which is BAD because it destroys the mozilla control but NOT the window containing it, shortly after which the whole thing crashes. Reproducible: Always Steps to Reproduce: 1. Write a container to load the moz activex ctrl. 2. Connect a DWebBrowserEvents2 event sink. 3. Load a page that executes 'window.close' in the javascript... Actual Results: No DISPID_WINDOWCLOSING event seen in the event sink. Expected Results: Sent a DISPID_WINDOWCLOSING event to the DWebBrowserEvents2 sink. The actual value of DISPID_WINDOWCLOSING is 263 and it should call: void WindowClosing(VARIANT_BOOL IsChildWindow, VARIANT_BOOL *Cancel);
Assignee: general → adamlock
Component: General → Embedding: ActiveX Wrapper
Product: Mozilla Application Suite → Core
QA Contact: general → dunn5557
Version: unspecified → Trunk
QA Contact: dunn5557 → activex
The ActiveX embedding API was removed in bug 662023 and friends, making this INVALID. [Filter bugspam on activexinvalid]
Assignee: adamlock → nobody
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.