Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-12963

When adding comments in PR with Korean/Chinese/Japanese language, the "Comments cannot be empty" error is thrown

XMLWordPrintable

      Issue Summary

      When adding comments in PR with Korean/Chinese/Japanese language, the "Comments cannot be empty" error is thrown

      Steps to Reproduce

      1. Setup a PR request on Bitbucket.
      2. Install a Korean(Or Chinese or Japanese) keyboard layout on your computer.
      3. Navigate to a pull request and Click Add Comment and type a comment in Korean or Chinese or Japanese. Then click "Comment" button to save it and you will see "Comments cannot be empty" error is thrown.
      4. Same is case when you edit and save an existing comment in Korean or Chinese or Japanese.

      Expected Results

      The comment typed should be saved.

      Actual Results

      The comment is not saved and "Comments cannot be empty" error is thrown.

      Workaround

      After typing the comment in Korean or Chinese or Japanese, press Right-Arrow or Enter key to release the Keyboard from language composition mode and then click Save or Comment button to successfully save the comment.

            [BSERV-12963] When adding comments in PR with Korean/Chinese/Japanese language, the "Comments cannot be empty" error is thrown

            Jemma Zhang added a comment -

            releasing 7.6.19

            Jemma Zhang added a comment - releasing 7.6.19

            Carlos Sanchez Rosa added a comment - - edited

            Hello, this issue is caused by the Codemirror library who doesn't trigger the change event while composing asian characters, we were able to add a couple of extra listeners to the input directly and fixed the bug from our side, no need to upgrade to v6 yet, the solution will be available in the following release.

            Carlos Sanchez Rosa added a comment - - edited Hello, this issue is caused by the Codemirror library who doesn't trigger the change event while composing asian characters, we were able to add a couple of extra listeners to the input directly and fixed the bug from our side, no need to upgrade to v6 yet, the solution will be available in the following release.

              cb3955cd8c67 Carlos Sanchez Rosa
              ephillips@atlassian.com Edward
              Affected customers:
              3 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: