New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only the first letter will be alphabetic when input Japanese. (using Japanese IME) #9709

Closed
Kurom96 opened this Issue Jun 9, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@Kurom96

Kurom96 commented Jun 9, 2017

  • Electron version: 1.7.2
  • Operating system: mac OSX El Capitan 10.11.6
  • Node version: 4.4.7, 7.2.1, 7.9.0

Expected behavior

We should be able to input Japanese in text-input on webview, using the Japanese IME to convert alphabets to Japanese.

Actual behavior

Immediately after application focus, and start typing Japanese input.
Only the first letter will be alphabetic.

How to reproduce

$ git clone https://github.com/Kurom96/electron-quick-start.git -b  japanese-input-bug
$ cd electron-quick-start
$ npm i
$ npm start

See bellow.

japanese-input-bug

Others

  • It does not occur under 1.7.1
  • Is this fix affected? #9173

@Kurom96 Kurom96 changed the title from Only the first letter will be alphabetic. (using Japanese IME) to Only the first letter will be alphabetic when input Japanese. (using Japanese IME) Jun 9, 2017

@kevinsawicki

This comment has been minimized.

Show comment
Hide comment
@kevinsawicki

kevinsawicki Jun 9, 2017

Contributor

@Kurom96 can you test the latest 1.6.x release as well?

Contributor

kevinsawicki commented Jun 9, 2017

@Kurom96 can you test the latest 1.6.x release as well?

@Kurom96

This comment has been minimized.

Show comment
Hide comment
@Kurom96

Kurom96 Jun 9, 2017

@kevinsawicki I tested it in 1.6.10, but this issue did not occur.

Kurom96 commented Jun 9, 2017

@kevinsawicki I tested it in 1.6.10, but this issue did not occur.

@kevinsawicki

This comment has been minimized.

Show comment
Hide comment
@kevinsawicki

kevinsawicki Jun 9, 2017

Contributor

I tested it in 1.6.10, but this issue did not occur.

@Kurom96 thanks, can you try 1.6.11 as well? It contains the same patch from #9173

Contributor

kevinsawicki commented Jun 9, 2017

I tested it in 1.6.10, but this issue did not occur.

@Kurom96 thanks, can you try 1.6.11 as well? It contains the same patch from #9173

@Kurom96

This comment has been minimized.

Show comment
Hide comment
@Kurom96

Kurom96 Jun 10, 2017

@kevinsawicki It did not occur in 1.6.11 either.

Kurom96 commented Jun 10, 2017

@kevinsawicki It did not occur in 1.6.11 either.

@kevinsawicki

This comment has been minimized.

Show comment
Hide comment
@kevinsawicki

kevinsawicki Jun 14, 2017

Contributor

Commented at https://bugs.chromium.org/p/chromium/issues/detail?id=714771#c23 asking for help from the Chrome team on this one.

Contributor

kevinsawicki commented Jun 14, 2017

Commented at https://bugs.chromium.org/p/chromium/issues/detail?id=714771#c23 asking for help from the Chrome team on this one.

@kevinsawicki

This comment has been minimized.

Show comment
Hide comment
@kevinsawicki

kevinsawicki Jun 14, 2017

Contributor

Looks like https://codereview.chromium.org/2929543002/ may address this, needs verification though.

Contributor

kevinsawicki commented Jun 14, 2017

Looks like https://codereview.chromium.org/2929543002/ may address this, needs verification though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment