| Summary: | [Browser] Cannot block default key handling of IE accelerators | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Markus Keller <markus.kell.r> |
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | Grant Gayed <grant_gayed> |
| Severity: | normal | ||
| Priority: | P3 | CC: | chrriis, daniel_megert |
| Version: | 3.5 | Keywords: | triaged |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
Markus Keller
That's probably a problem in IE 8. I'm pretty sure the fix for bug 222024 used to work at some time but now I get that location dialog also in 3.4.2. It looks like the specific failure case is blocking of KeyDowns that correspond to IE accelerators, so changing report title accordingly. Showing the Open Location dialog when Ctrl+L is pressed is a new one for IE8, but others like Ctrl+A and Ctrl+P fail as far back as IE6. Blocking of other keys seems fine in IE8. Some users have an issue with default IE accelerators. There does not seem any way to block accelerators and this causes problems: they control the content but certain accelerators cause errors at their PHP end. For example: F5 refreshes the current page which has nasty effects. Backspace is legal when in a text field but has a nasty effect (back navigation) when no text field has the focus. Is there a way to shortcut all default IE accelerators? This is a one-off bulk update. (The last one in the triage migration). Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process: https://wiki.eclipse.org/SWT/Devel/Triage See Bug 518478 for details. Tag for notification/mail filters: @TriageBulkUpdate This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |