The short answer to the original question is: No. When a text attribute is unlocked it is part of a within a textarea ; and when the page is saved the content of the textarea posted back to the database. When a text attribute is locked it is pat of a table cell only, i.e. shown on screen only and not part of the ; and when page is saved not posted back to server. Now. The "presentation layer" is performed by the browser (not Clarity). When unlocked the browser contains the text within the textarea and applies rendering rules of a textarea (this form control allows for width and height and scrolling). When locked the browser contains the text in a table cell (subject to .css frmatting) and renders the text according to these standards (without width, height, scrolling). This is "as designed" - no question. In addition the example screenshot uses many 1's + many 2's etc without spaces. This won't wrap because the browser rendering cannot find spaces to wrap at. You may go ahead with a case, but it isn't a bug.