Bug #15437
IBus input of Japanese and Korean characters is broken in Tor Browser
Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Internationalization
Target version:
Start date:
2018-03-22
Due date:
% Done:
100%
Description
Reported by several users. Still needs to be tested on Debian:
Since Tails 3.6rc1 users cannot input Japanese text in Tor Browser. It works in other programs in Tails, such as the Text Editor, but it does not work on TBB nor the Unsafe Browser.
To reproduce:
- Start Tails in Japanese with Japanese keyboard
- Write things in Text editor and Tor browser.
Corresponding bug reports: 43c31f44a97dda68c59989049f0d9c59, bfee9b4c138c78ae1c809794588f861f
Subtasks
Related issues
Blocks Tails - |
Resolved | 2017-06-29 |
History
#1 Updated by intrigeri 2018-03-22 11:34:16
- Description updated
#2 Updated by intrigeri 2018-03-22 12:25:34
- Subject changed from Tor Browser cannot input Japanese or Korean ibus characters to IBus input of Japanese and Korean characters is broken in Tor Browser
#3 Updated by intrigeri 2018-03-22 12:40:14
- Status changed from New to Confirmed
- Assignee set to intrigeri
- Priority changed from Normal to Elevated
- Target version set to Tails_3.7
- QA Check deleted (
Info Needed)
That’s another regression caused by Bug #12679.
#4 Updated by intrigeri 2018-03-22 12:40:24
- blocks
Feature #13245: Core work 2018Q1: Foundations Team added
#5 Updated by intrigeri 2018-03-22 12:43:10
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 10
- Feature Branch set to bugfix/15437-IBus-in-Tor-Browser, torbrowser-launcher.git:bugfix/15437-IBus-in-Tor-Browser
#6 Updated by intrigeri 2018-03-22 14:22:18
- Assignee changed from intrigeri to anonym
- % Done changed from 10 to 50
- QA Check set to Ready for QA
#7 Updated by intrigeri 2018-03-27 10:15:00
- Target version changed from Tails_3.7 to Tails_3.6.2
#8 Updated by anonym 2018-03-29 10:04:26
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
#9 Updated by anonym 2018-03-30 16:59:44
- Status changed from Fix committed to Resolved