Thanks for reporting the issue ..

@vishvas.vasuki-- Could you please let us know detailed steps to set up the hi-optitransv2 input (from m17n) in ubuntu 14.04 and a screencast would help us in better understanding.

Thanks!

namaste hdodda - Firstly, thanks for taking a look - it rekindles hope. 
I don't have access to ubuntu 14.04, as I run 17.04. But I have added this comment - https://bugs.chromium.org/p/chromium/issues/detail?id=605564#c6 which should provide clues as to how to do it for 14.04 as well.

Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested the issue on ubuntu 14.04 using chrome M62 #62.0.3202.45 with the steps mentioned in comment #3 and observed that issue is not reproduced.

Attached screencast for reference.

Note : Couldn't find hindi languages in text entry after installing ibus in ubuntu 17.04..

@Could you please check in latest beta and confirm us with your observations.

Thanks!

Deleted: 772691.ogv 5.9 MB

	772691.ogv 5.9 MB View Download

@hdodda - Thanks for checking. I confirm that the particular string I first pointed to years ago is transliterated properly. But not several other strings, such as what I described in comment 3. Please see https://bugs.chromium.org/p/chromium/issues/detail?id=605564#c7 for details.

Not sure why you're not getting hindI - Perhaps restarting everything will make it show up..

Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Also, regarding the missing input methods - try https://bugs.chromium.org/p/chromium/issues/detail?id=605564#c8 .

vishvas.vasuki@ Thanks for the feedback.

Re-tested the issue on Ubuntu 16.04 using chrome latest beta 62.0.3202.45 with the below steps.

1. Launched Chrome and installed iBus m17n package to Ubuntu 16.04.
2. Restarted the system and navigated to TextEntry in menu and clicked on '+' to choose a language.
3. Selected Hindi(itrans(m17n)) from the list.
4. Opened a text area and changed the system language to Hindi(itrans(m17n)).
5. Typed 
dalanatas sphuritais sphuTaphUtkRtaiH
svakaramaskaragarvitataskaraH  in the text area and could observe that the result in Hindi is as mentioned in comment #7 in issue 605564.
Please find the attached screen shot for reference.

Checked this is M50 chrome builds as well and could observe the same behavior.

Request you to please check and confirm if there is any issue or this is the expected behavior? Please update the thread if anything is missing from our end.

Thanks..

Deleted: 605564.png 184 KB

	605564.png 184 KB View Download

@susanjunaib - Comment 7 refers to  https://bugs.chromium.org/p/chromium/issues/detail?id=605564#c3 , and if you see the video therein, you'll see that you were supposed to try typing it in Google Sheets and whatsapp web. Can you please see the video and retry?

Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

vishvas.vasuki@ - Thanks for the issue..

Able to reproduce the issue on Ubuntu 16.04 stable version #61.0.3163.100 and Beta 62.0.3202.45.

Bisect Information:
=====================
Good build: 57.0.2951.0	 Revision(438385)
Bad Build : 57.0.2952.0	 Revision(438707)

Unable to provide the changelog using the per-revision script and normal bisect, as all bad builds are invoked.

Below is the changelog from manual Bisect from Omahaproxy.

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/57.0.2951.0..57.0.2952.0?pretty=fuller&n=10000

From the above change log suspecting below change
Review URL: https://codereview.chromium.org/2518183002

nektar@  Could you please check whether this issue is related with to your change, if not please help us in assigning it to the right owner. 

Thanks...!!

Please note that, as mentioned in https://bugs.chromium.org/p/chromium/issues/detail?id=605564#c5 , this is a problem in other blink-based browsers as well.

For triaging.

Blink bug therefore:
- This does not appear to be explicitly accessibility related; however, it is related to a change made by @nektar, so I will keep it in our component. 
- changing component to Blink>Accessibility 
- assigning label of a11y-secondary 

Making untriaged since I need a dev's input as to if this should be a Pri1 or Pri2.