Bug 26518
| Summary: | Square brackets ('[' and ']' : Gmail keyboard shortcut) not working properly with Italian keyboard | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | xlyuan |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ahmad.saleem792, ap, bfulgham, cira, hbono, jshin, rniwa, simon.fraser, zalan |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
xlyuan
Build: Webkit nightly build r44781 (2009-06-18)
OS: Windows, not test on Mac
Other Browsers:
Chromium: Fail
Firefox3.0.11: OK
IE8: Fail
Steps:
1. Launch Safari
2. Sign in Gmail
3. Click the "Inbox" link
4. Open one of the incoming email
5. Switch to Italian keyboard
6. Hit AltGr + '[' or ']'
>>AltGr is the right Alt key
7. Observe
Result:
Gmail doesn't archive and move to the previous or next email
Expected:
Gmail should archive and move to the previous or next email
Notes:
Gmail by default assigns '[' and ']' to archive and move to previous or next email, it works with English keyboard but not with foreign keyboards
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
xlyuan
This issue is also tracked in Chromium as crbug.com/14352
Jungshik Shin
sorry for bug spam !
Nebojša Ćirić
Standard Serbian keyboard layout doesn't even have "[]{}" characters. Do we fix this only for layouts that can produce '[' and ']' with some combination of key presses?
Jungshik Shin
(In reply to comment #3)
> Standard Serbian keyboard layout doesn't even have "[]{}" characters. Do we fix
> this only for layouts that can produce '[' and ']' with some combination of key
> presses?
If that's the case, isn't it a gmail issue that '[' and ']' are not good choice for some KBD layouts? You have to file a bug ('feature request') against gmail, don't you?
This bug is about '[' and ']' not working in gmail + Webkit-on-Windows on KBD layouts where it IS possible to type them (and it works with Firefox and Opera + gmail).
Ahmad Saleem
Don't have test case to reproduce but this was fixed in Chrome / Blink around 2017 to 2018 time:
https://chromium.googlesource.com/chromium/src.git/+/e22d04949d069f7184b3233d1b83e26fe79e1bcc
https://chromium.googlesource.com/chromium/src.git/+/e66269c362f753cd57f5bf5bc8d33c7c81bbbdce
https://chromium.googlesource.com/chromium/src.git/+/6a2637c75c821987e58ef6ab8bacce54fb9078c0
https://chromium.googlesource.com/chromium/src.git/+/f72e9811866f116f60684110efc749c0890dce60
https://chromium.googlesource.com/chromium/src.git/+/de04a533c1efcbeefae7ec4f3eb4cb937da5d157
https://chromium.googlesource.com/chromium/src.git/+/891184d01481bfe9af1318345ca22211ff53e020
Comment 01 refers to the Chrome bug, which got merged into this: https://crbug.com/25503
Is it something we need to look into? Thanks!