Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-25173

Non ascii comment content is corrupted when using the new Quick Comment mechanism (except for Firefox users)

XMLWordPrintable

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Hi,

      There is our customer's report.
      Non-ascii characters that are contained in a comment added in page are broken.
      (Please see the attached screenshot.)

      The validated result by each web clients:

      OS Browser Result
      Windows 7 IE9
      Windows 7 Chrome
      Windows 7 Firefox
      Mac OS X Safari

      This problem's impact is very critical. Please fix it immediately.

      Best regards,
      Kan Ogawa
      Ricksoft support

        1. CONF-25173_ScreenShot.png
          CONF-25173_ScreenShot.png
          134 kB
        2. ConfJapaneseComment.jpg
          ConfJapaneseComment.jpg
          81 kB

            [CONFSERVER-25173] Non ascii comment content is corrupted when using the new Quick Comment mechanism (except for Firefox users)

            Michael Knight added a comment -

            Hi Aleksy,

            This happens when an issue has been fixed in the codebase but (in the case of OnDemand) may not have been deployed yet. In this case the deployment is happening right now during the usual weekly OnDemand maintenance period.

            Michael Knight added a comment - Hi Aleksy, This happens when an issue has been fixed in the codebase but (in the case of OnDemand) may not have been deployed yet. In this case the deployment is happening right now during the usual weekly OnDemand maintenance period.

            Alexey Pikulik added a comment -

            Why does this issue has status Resolved if the problem is not fixed yet?

            Alexey Pikulik added a comment - Why does this issue has status Resolved if the problem is not fixed yet?

            Paul Curren added a comment -

            Yes, Exmuzzy is correct. The 'Edit' function still uses the traditionally loaded editor. So if you post and then immediately edit you will be able enter the required text.

            However this requires you to make your comment twice. I think the better approach going forward is still to disable the quick-comments plugin.

            Paul Curren added a comment - Yes, Exmuzzy is correct. The 'Edit' function still uses the traditionally loaded editor. So if you post and then immediately edit you will be able enter the required text. However this requires you to make your comment twice. I think the better approach going forward is still to disable the quick-comments plugin.

            Alexander Korolev added a comment -

            The other work-around is to edit twice new comment!

            Alexander Korolev added a comment - The other work-around is to edit twice new comment!

            Paul Curren added a comment -

            The only work-around for the moment is to go to the plugins administration screen and turn off the quick-comments plugin. Confluence will revert to using the old commenting mechanism which does not have this problem.

            Paul Curren added a comment - The only work-around for the moment is to go to the plugins administration screen and turn off the quick-comments plugin. Confluence will revert to using the old commenting mechanism which does not have this problem.

            Hanis Suhailah (Inactive) added a comment -

            any workaround for the time being?

            Hanis Suhailah (Inactive) added a comment - any workaround for the time being?

            Stefan Saasen (Inactive) added a comment -

            Updated fixversion from 4.2.1 to 4.2.2. 4.2.1 has already been built.

            Stefan Saasen (Inactive) added a comment - Updated fixversion from 4.2.1 to 4.2.2. 4.2.1 has already been built.

            Paul Curren added a comment -

            The jQuery documentation states that the data will always be transmitted as UTF-8 by default. However it is only on Firefox that the correct 'charset' value is set on the 'content-type' header.

            The fix is to explicitly set the charset.

            Paul Curren added a comment - The jQuery documentation states that the data will always be transmitted as UTF-8 by default. However it is only on Firefox that the correct 'charset' value is set on the 'content-type' header. The fix is to explicitly set the charset.

            Sean Osawa (Inactive) added a comment -

            Commenting does not work with Japanese characters from Chrome and Safari on the latest Confluence. It definitely blocks everyday's work on Confluence.
            Here's my test results:

            OS Browser Result
            Mac OS X Chrome
            Mac OS X Safari
            Mac OS X Firefox

            Sean Osawa (Inactive) added a comment - Commenting does not work with Japanese characters from Chrome and Safari on the latest Confluence. It definitely blocks everyday's work on Confluence. Here's my test results: OS Browser Result Mac OS X Chrome Mac OS X Safari Mac OS X Firefox

            Sean Osawa (Inactive) added a comment -

            Updated priority from Major to Blocker.

            Sean Osawa (Inactive) added a comment - Updated priority from Major to Blocker.

              pcurren Paul Curren
              f9ced3a62372 Kan Ogawa
              Affected customers:
              6 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: