If Single Page Application functionality is disabled, non ASCII characters are broken

• Type: Regression Bug
• Status: Closed
• Resolution: Duplicate
• Affects Version/s: 7.0.0 DXP FP12, 7.0.X EE, Master
• Fix Version/s: 7.0.X EE, Master
• Component/s: Core Infrastructure
• Labels:
  • DXPJPLOCAL
  • DXPJPUI
  • QA-AUTOMATION
  • QA-V
• Flagged:
  Impediment
• Fix Priority: 5

Summary
Liferay allows Single Page Application (SPA) functionality to be disabled by setting javascript.single.page.application.enabled=false. After starting up with SPA disabled, inputting any non-ASCII character into Control Panel fields results in broken encoding.

We have tested the following languages and have found that non-ASCII characters appear broken:

• Arabic
• Korean
• Japanese
• Languages that utilize accented characters like (á,ô,ü,å) – example, á is rendered as á

This affects a user's account information (e.g. all fields in My Account), Site Name, Role names, and more. The only part that we tested that preserved the original names were site content, and page names.

Steps to Reproduce
1. Configure "javascript.single.page.application.enabled=false"
2. Restart Liferay
3. Multi bytes characters are displayed correctly at this point
4. Rename a Site name, e.g., from "Liferay" to "ライフレイ", and Save

Actual Result
The site name are scrambled like "ライフレイ"

Expected Result
Site name will appear as "ライフレイ"

Note
If we add the localization tag to the URL (e.g. /en), the text is preserved properly. For example:

http://localhost:8080/en/group/control_panel/manage?p_p_id=com_liferay_my_account_web_portlet_MyAccountPortlet

• enter non english characters アアア
• save
  Result: Inputted characters are preserved アアア

Reproduced in
ee-7.0.x - 85f69a92d921bd400fc42b11c4b9a704fd9839ba
DXP + Fix Pack DE-12

Did not test in
Master