User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 http://sspsoft.com/dhtml/win1.html Click on Test Window(Title Bar area), this window will come up. Now move mouse to Search Input Box. Right Click to see Context Menu, it appaers at wrong position. This happens all the time when 2 or more IFRAMES are overlapped. The first loaded iframe will get focus and rest won't. The CSS z-index property will show it correct but that is not right. I tried even, document.getElementById('ifrm').contentWindow.focus() as suggested in your docs, that does not work either. Reproducible: Always Steps to Reproduce: 1. GO to http://sspsoft.com/dhtml/win1.html 2. Click on Test Window(Title Bar area), this window will come up. 3. Now move mouse to Search Input Box. Right Click to see Context Menu, it appaers at wrong position. Actual Results: The 1st iframe tag will retain focus. Even js tried to set focus for other iframe, it will not do it. Will not show any error. Expected Results: Focus should be able to transfer on request, including IFRAME TAGS
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050330 Firefox/1.0+ WFM - Reporter, can you try with a nightly trunk build to see if this is still an issue please? http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2005-03-30-07-trunk/
dupeme 131784 As per comments in 131784, clicking on the frame around the iframe will give focus. Mozilla does not currently handle the focus events on iframes directly.
(In reply to comment #1) > Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050330 > Firefox/1.0+ > WFM - Reporter, can you try with a nightly trunk build to see if this is still > an issue please? > http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2005-03-30-07-trunk/ Confirm. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050330 Firefox/1.0+ Difference between Wind2k and WinXP (NT5 vs NT 5.1) perhaps?
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.