User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 When the Flash plug-in calls SetFocus as a result of a mouse click in a text field, Mozilla does not give up its belief that it has the focus. In Netscape 4, it did. In all versions of Netscape and Mozilla since 4, it does not. Reproducible: Always Steps to Reproduce: 1. Put a Flash movie containing a text field on an HTML page which contains an HTML text field. 2. Click on the HTML text field - note blinking cursor and ability to type. 3. Click on the Flash text field - note there are now blinking cursors in both text fields, and that typing sends characters to Flash. 4. Click on the HTML text field again - note that nothing changes, and that typing continues to send characters to Flash. Actual Results: Once both Flash and Mozilla both think they have focus, all character messages go to Flash. Expected Results: Mozilla should give up focus when Flash calls SetFocus on its own HWND. If it did so, then when the user clicked back into the HTML text field, Mozilla woull call SetFocus itself, resulting in a WM_KILLFOCUS message being sent to Flash so that Flash knows to release the focus. It is easy to test this. If you click on Flash first, and then click on the HTML text field, Mozilla realizes it is getting the focus and tells Flash to release focus. But if you click on HTML first, when you then click on Flash Mozilla does not let go.

zip contains HTML and SWF to demonstrate bug.

Note to self - Flash player bug 46998

fixed by bug 235294 ?

*** This bug has been marked as a duplicate of 306209 ***