Bugs item #652638, was opened at 2002-12-12 04:31 Message generated for change (Comment added) made by shawnkhall You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=432066&aid=652638&group_id=42081
Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Win-S shows IE context menu on XP Initial Comment: Win-S activates the search field but then it shows the same context menu IE shows if you right click inside an edit field or textarea. So I must always press ESC after Win-S before I can enter a search text. System: Windows XP Pro, IE6. ---------------------------------------------------------------------- >Comment By: Shawn K. Hall (shawnkhall) Date: 2005-01-25 06:09 Message: Logged In: YES user_id=219805 This was resolved with the 3.1.8 double-clicking/double-focus problems. ---------------------------------------------------------------------- Comment By: mll (mlmll) Date: 2003-01-10 00:58 Message: Logged In: YES user_id=491129 Too bad I can't reproduce this either on WinXP Home SP1 or on Win2K SP3, both with IE6.0 SP1. In other words, I get the excpected behaviour fo Win+S. MLL ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-01-10 00:25 Message: Logged In: NO The hotkey works. That wasn't the problem. The problem is that no matter what hotkey combination activates the search field it (on XP + IE6) also shows the same right-click menu that IE shows if you right click inside a textfield. I.e. I press the hotkey combination (WIN+S or whatever) => the focus is set to the search bar textfield but the annoying popup menu is shown which I must close before I can enter anything in the search bar's textfield. I consider it a bug, not serious but certainly annoying.... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-01-09 18:32 Message: Logged In: NO Preferences.js file explains 3 variables that can be set to change the default hot-key. So the hotkey is actually changeable, which would work around your problem. I believe (as an ordinary end-user of QSD) --as QSD already has the flexibility to change the hotkey-- this shouldn't be considered a bug. Changing the default hot key would upset many users who are used to the current setting. A documentation addition can be done though, which suggests XP users to set hot-key preference through localprefs.js file. Or the installer may be clever enough to set it to something else when installed on a clean XP system. But being a developer myself, I'd consider this "Not-an-issue"! ;) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=432066&aid=652638&group_id=42081 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
