Closed
Bug 280253
Opened 20 years ago
Closed 19 years ago
Tab (focus), Backspace, & Arrow keys not working with embedded ActiveX Control in Internet Explorer
Categories
(Core Graveyard :: Embedding: ActiveX Wrapper, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: daseymour, Assigned: adamlock)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox (3HC Customized Version)/1.0 Build Identifier: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; iOpus-I-M; .NET CLR 1.1.4322; .NET CLR 1.0.3705) With the Mozilla ActiveX Control (1.7.1) embedded inside Internet Explorer, the following happens... When using HTML (or XUL) form controls (such as INPUT) within the Mozilla control, ... 1. The TAB key changes the focus to other controls within Internet Explorer, not the controls within the Mozilla control. 2. The BACKSPACE key causes Internet Explorer to navigate backwards through the browser history. 3. The Arrow keys don't seem to function at all. Because the Mozilla control uses ATL, I believe this problem can be resolved by implementing the resolutions provided in the following pages... PRB: Backspace in ATL Subclassed CTL Causes Internet Explorer to Navigate Back http://support.microsoft.com/?kbid=190044 PRB: Focus and Tab Issues with ATL Subclassed Edit Control http://support.microsoft.com/?kbid=179696 Reproducible: Always Steps to Reproduce: (see above)
Reporter | ||
Comment 1•20 years ago
|
||
To view a testcase, visit the URL listed above using Internet Explorer (or go to http://www.seymoursolutions.com/support/bugs/other/mozbug2.php )
Reporter | ||
Comment 2•19 years ago
|
||
Here's another article on a possible resolution... PRB: Windowless ATL Control Does Not Receive Focus Messages in Internet Explorer http://support.microsoft.com/?kbid=318034
Comment 3•19 years ago
|
||
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/
Comment 4•19 years ago
|
||
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
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•12 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•