Opera: Difference between revisions

From miki
Jump to navigation Jump to search
(→‎Bugs: Bug report on keyboard setup)
 
Line 1: Line 1:
== Bugs ==
== Bugs ==
=== Bug report ===
=== Bug report bug-361427@bugs.opera.com ===
* <u>Type</u>: Other problem / NotSure/Other
* <u>Type</u>: Other problem / NotSure/Other
* <u>Summary</u>: Keyboard setup changes key shortcut for non-latin keys (AZERTY keyboard)
* <u>Summary</u>: Keyboard setup changes key shortcut for non-latin keys (AZERTY keyboard)

Revision as of 10:04, 10 September 2008

Bugs

Bug report bug-361427@bugs.opera.com

  • Type: Other problem / NotSure/Other
  • Summary: Keyboard setup changes key shortcut for non-latin keys (AZERTY keyboard)
  • How to reproduce:
    1. Get an AZERTY keyboard (eg. Belgian keyboard)
    2. Open the keyboard setup dialog (in preferences -> keyboard shortcuts -> edit any keyboard configuration)
    3. Edit any shortcut, and use '²' as the wanted key shortcut ('³' is the exponent-2 key located at top left of keyboard; on qwerty, it is the back-apostrophe/tilde key).
    4. Close dialog, reopen again, and check shortcut. Shortcut key has been changed to something else.
    5. Back in browsing mode, check that the shortcut '²' doesn't work indeed
  • Expected: I expected the keyboard shortcut action to trigger
  • Happened: Nothing happens. no actions. It is possible to circumvent the bug by manually editing the .ini file, and copy-pasting the utf8 encoding of the keyboard shortcut key (in my case '²' is encoded as 0xC2 0xB2)
  • Platform: Opera 9.50 / Windows