Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Entering multiple lines in a text box & display from upper left corner

Avatar

Former Community Member

I have forms where a large amount of comment might be entered into the form - maybe a whole page.  When I create a large text box and allow multiple lines, the text entered currently displays in the center of the box and expands to fill the box, up or down, from the center.  Is there a way to have force the entered text to appear at the upper left corner of the box and flow down.  If this was a box that people were writing in, that is the way they would do it.

Thank you for the assistance.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Click on the object and on the Font palette (it might not be visible - you can activate it under the Window menu) click on the Paragraph tab on on that menu you can choose the text alignment.

paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Click on the object and on the Font palette (it might not be visible - you can activate it under the Window menu) click on the Paragraph tab on on that menu you can choose the text alignment.

paul

Avatar

Former Community Member

Thanks, Paul.  This worked perfectly.  Why don't they show this more prominently in any documentation? (You don't need to answer that question ;-))

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----