# Since version 1.0, Japanese inline input has become difficult to use

**URL:** <https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009>\
**Category:** General\
**Created:** [11 December 2019 00:27 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009 "2019-12-11T00:27:40Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![utaani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/utaani/32/102_2.png) [@utaani](https://discourse.nodered.org/u/utaani)\
**Post date:** [11 December 2019 00:27 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/1 "2019-12-11T00:27:40Z")

</div>

There was no problem in the version before 0.20, but it became 1.0, and it became difficult to use Japanese input with IME in the text area of ​​multi-line input.

![0.20.7](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/b/b3994fac27eb41b4a4fc00a97d4caa40356957ec.png) ![1.0.3](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/c/c34fe7b1fbeb82e102a6d9eed566f08ffe73c533.png)

I guess it is due to the change of the library of the text area of ​​multi-line input. I think it's the same for other languages ​​that use IMEs.

---

<div class="post-metadata">

**Author:** ![okhiroyuki](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/okhiroyuki/32/15056_2.png) [@okhiroyuki](https://discourse.nodered.org/u/okhiroyuki)\
**Post date:** [12 December 2019 04:31 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/2 "2019-12-12T04:31:52Z")

</div>

There seems to be no problem with the following combinations.

- OS: Mac Catalina
- IME: Google IME
- Node-RED@1.0.3
- Node.js@10.13.0

Is this a problem specific to Windows?

 ![スクリーンショット 2019-12-12 13.22.29](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/c/c0de9935091b2be471b7eeb37fc8b51ca7ef0f8a.png)

---

<div class="post-metadata">

**Author:** ![okhiroyuki](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/okhiroyuki/32/15056_2.png) [@okhiroyuki](https://discourse.nodered.org/u/okhiroyuki)\
**Post date:** [12 December 2019 04:42 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/3 "2019-12-12T04:42:57Z")

</div>

By the way, ace.js doesn't seem to be updated from 0.20.4.

- 0.20.4: ace@1.4.3 [https://github.com/node-red/node-red/releases/tag/0.20.4](https://github.com/node-red/node-red/releases/tag/0.20.4)
- 0.20: ace@1.4.1 [https://github.com/node-red/node-red/releases/tag/0.20.0](https://github.com/node-red/node-red/releases/tag/0.20.0)

---

<div class="post-metadata">

**Author:** ![kazuhitoyokoi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kazuhitoyokoi/32/621_2.png) [@kazuhitoyokoi](https://discourse.nodered.org/u/kazuhitoyokoi)\
**Post date:** [13 December 2019 06:29 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/4 "2019-12-13T06:29:55Z")

</div>

On the latest Chrome and Firefox on Windows 10, I encountered the same problem in Node-RED v1.0.3. There's no problem on Internet Explorer. The object name of the horizontal scroll bar seems to be "composition" but there's no information to solve the problem on the Internet.

I also tried the following procedures to update ace but the result is the same.

> **[node-red/node-red](https://github.com/node-red/node-red/tree/master/packages/node_modules/%40node-red/editor-client/src/ace)**
>
> Low-code programming for event-driven applications - node-red/node-red

---

<div class="post-metadata">

**Author:** ![utaani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/utaani/32/102_2.png) [@utaani](https://discourse.nodered.org/u/utaani)\
**Post date:** [15 December 2019 23:44 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/5 "2019-12-15T23:44:23Z")

</div>

It seems on firefox 71 / Chrome 79 with windows 10 windows IME.

---

<div class="post-metadata">

**Author:** ![utaani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/utaani/32/102_2.png) [@utaani](https://discourse.nodered.org/u/utaani)\
**Post date:** [15 December 2019 23:48 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/6 "2019-12-15T23:48:30Z")

</div>

I tried it with a plain sample program of ace editor 1.4.3, but I didn't see any problems with Japanese inline input in Node-RED 1.0.3.  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/8/80bdffb38d327bc0e721ea82d9daf68672ac87ff.png)

---

<div class="post-metadata">

**Author:** ![kazuhitoyokoi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kazuhitoyokoi/32/621_2.png) [@kazuhitoyokoi](https://discourse.nodered.org/u/kazuhitoyokoi)\
**Post date:** [17 December 2019 12:05 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/7 "2019-12-17T12:05:52Z")

</div>

I modified CSS as follows. It seems to work correctly on the latest Chrome, Firefox and IE on Windows 10 (I haven't checked browsers on macOS yet).

> <https://github.com/kazuhitoyokoi/node-red/commit/9cbd0fceeafb7aee60498f39aec025b9f9bdf14c>

---

<div class="post-metadata">

**Author:** ![kazuhitoyokoi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kazuhitoyokoi/32/621_2.png) [@kazuhitoyokoi](https://discourse.nodered.org/u/kazuhitoyokoi)\
**Post date:** [18 December 2019 04:00 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/8 "2019-12-18T04:00:39Z")

</div>

On my Safari, Chrome, and Firefox on macOS, it worked correctly. Therefore, I submitted the following pull request.

> <https://github.com/node-red/node-red/pull/2411>

---

<div class="post-metadata">

**Author:** ![utaani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/utaani/32/102_2.png) [@utaani](https://discourse.nodered.org/u/utaani)\
**Post date:** [18 December 2019 04:23 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/9 "2019-12-18T04:23:42Z")

</div>

After applying the presented patch and checking it with Firefox / Chrome on Windows 10, it can now be displayed correctly!  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/5/5490544d78307846c67b804e8bdbeeb61e665b3a.png)

---

<div class="post-metadata">

**Author:** ![kazuhitoyokoi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kazuhitoyokoi/32/621_2.png) [@kazuhitoyokoi](https://discourse.nodered.org/u/kazuhitoyokoi)\
**Post date:** [18 December 2019 04:35 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/10 "2019-12-18T04:35:19Z")

</div>

@utaani Thank you for checking the patch, Ueno-san!

---

<div class="post-metadata">

**Author:** ![utaani](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/utaani/32/102_2.png) [@utaani](https://discourse.nodered.org/u/utaani)\
**Post date:** [18 December 2019 04:37 UTC](https://discourse.nodered.org/t/since-version-1-0-japanese-inline-input-has-become-difficult-to-use/19009/11 "2019-12-18T04:37:42Z")

</div>

On Firefox  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/a/a6a6149cb91d8e0d53165138f795a9b04dc8cc56.png)