Red Hat Bugzilla – Bug 1027033
Zero width non breaking space in project description causes an exception when opening the project
Last modified: 2015-07-21 22:20:18 EDT
Description of problem:
If the user manages to copy a ZWNBS into their new project description, it will save fine but then fail with an exception when displaying the project.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Sign in, go to Projects->Create New Project
2. Enter a valid project id, project name
3. Enter some text into the description, including a ZWNBS (uc. 0xFEFF)
4. Press Save
An exception is thrown
The character should be rejected, or otherwise handled gracefully
The project is actually saved, and shows in the list, but is inaccessible.
Created attachment 820078 [details]
Test run log file
Attach (tail -n 1000 of) the test log
Caused by: line 1:1: unexpected char: 0xFEFF
at org.jboss.seam.text.SeamTextLexer.nextToken(SeamTextLexer.java:230) [jboss-seam-2.3.1.Final.jar:2.3.1.Final]
Ah, SeamText is exploding again. Fantastic.
That's on line 1, so in this case it's probably meant to be acting as a BOM (Byte Order Mark).
Issue should be fixed in 3.4.1. Please retest this.
Zanata 3.4.2-SNAPSHOT (git-server-3.4.1-1-g722ff43)
Zanata 3.5.0-SNAPSHOT (git-server-3.4.1-36-gd5f92ff)
After inserting 0xFEFF in About and Saved, About is not shown.
1. Login as a project maintainer or admin.
2. Go to a the project that you can maintain
3. Click Setting - > About (at buttom of Permissions)
4. Type "Test ZWNBS", and paste a ZWNBS from gucharmap
5. Save notes
6. Click About tab on the right of Maintainers
About Page was empty.
"Test ZWNBS" should be shown.
Just tested in Zanata 3.7, seems working fine now. Can you please retest this?
Let's wait until Bug 1198433 Verified.
Seem to fixed as a by-product of Bug 1198433.
The bug was no longer reproducable with Zanata 3.7.0-SNAPSHOT (git-jenkins-zanata-server-build-integration-master-5281)
This would have been fixed by the removal of Seam Text in 3.7, so I want to mark it as RELEASE_PENDING for now. Bugzilla won't let me do that from the CLOSED state, which is why I'm reopening.
For better tracking, I set the target-release 3.7