New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 648282 link

Starred by 3 users

Issue metadata

Status: Archived
Owner:
Closed: Dec 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

Hebrew Vowels (niqqud) cannot be typed with Hebrew keyboard layout in Chrome OS

Reported by jkno...@wisewildcats.org, Sep 19 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8350.68.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
Platform: 8350.68.0 (Official Build) stable-channel peppy

Steps to reproduce the problem:
1. Use Hebrew Keyboard.
2. Attempt to insert vowels.
3. 

What is the expected behavior?
Keyboard should possess an option to enter niqqud (Hebrew vowels).

What went wrong?
There appears to be no way to type Hebrew vowels, even in Google docs, which accepts Hebrew vowel input from other operating systems.

Did this work before? N/A 

Chrome version: 52.0.2743.116  Channel: n/a
OS Version: 8350.68.0
Flash Version: Shockwave Flash 22.0 r0
 
Components: -UI UI>Input>Text
Labels: OS-Android
Owner: omrilio@chromium.org
Status: Assigned (was: Unconfirmed)
omrilio@ can you confirm/comment?
Owner: warx@chromium.org
Tried on all methods I know of for adding vowels, none worked.
warx@ how hard would you think it would be to add such support
See: https://en.wikipedia.org/wiki/Niqqud#Macintosh as an example

Comment 3 by warx@chromium.org, Sep 20 2016

Not sure on this part. But I am interested to take a look.

Comment 4 by js...@chromium.org, Sep 22 2016

Cc: xiangye@chromium.org
Labels: -OS-Android
Summary: Hebrew Vowels (niqqud) cannot be typed with Hebrew keyboard layout in Chrome OS (was: Hebrew Vowels Inaccessible from Chrome OS)
 abodenha@: why did you add OS=Android? Chrome on Android does not have its own kbd but it just relies on whatever keyboard/IME OS has (either out of the box or user-installed kbd apps). 

Comment 5 by js...@chromium.org, Sep 22 2016

Xiangye@, can you get warx@ in touch with a team that has worked on CrOS input ? Thanks

Cc: -xiangye@chromium.org shuchen@chromium.org

Comment 7 by js...@chromium.org, Sep 25 2016

Cc: talo@chromium.org
shuchen@: what'd be the best way to implement one of methods described in  https://en.wikipedia.org/wiki/Niqqud ? 

BTW, we need to figure out which is the most widely used (and/or the best)  method (among those described above)
I think the best way to implement it is to define a new XKB symbol file with dead keys (like how we input ĕ, á, etc. in US International keyboard).

Comment 9 by leonelf@google.com, Feb 9 2018

Hello team, is there any update on this feature request?

Comment 10 by warx@chromium.org, Feb 9 2018

Cc: -shuchen@chromium.org
Owner: shuchen@chromium.org
Any updates?
Cc: xiangye@chromium.org shuchen@chromium.org
Owner: js...@chromium.org
jshin@, I feel this would require some inputs from i18n team for the CrOS keyboard layout standards. Something like this:
https://docs.google.com/presentation/d/19rS9q8Rf6NxcDk_iXdPB14PQfmeNniUrMtS4Q5LBvo4/edit#slide=id.ga28ac0e9e_0_68

I can help to update the XKB symbol file per the requirements.

Comment 13 Deleted

Thanks for keeping this conversation going. Our elementary school could convert entirely to Chrome OS were this feature were available.
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!
Status: Archived (was: Assigned)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.

Sign in to add a comment