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

Non-breaking space? Fixing right justified text in drop down list.

Avatar

Level 2

When I right justify the text for the items in my drop down list, the control's down arrow partially obstructs the right-most character.  I thought I might be able to add a non-breaking space to the right of the text, thus pushing it to the left, and out from under the arrow.  Is there a non-breaking space character recognized by LC in this context? If so, how do I create it?  Am I overlooking a simpler solution?  Thanks.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Interesting. While the "marginRight" attribute does not exist for a dropdown list object "para" node, you can set the "marginRight" attribute. Try this...

// form1.page1.subform1.DropDownList1::initialize - (JavaScript, client)

DropDownList1.para.marginRight = "5pt";

Steve

View solution in original post

13 Replies

Avatar

Former Community Member

I don't see the same behaviour.

Are you talking about Design view

dropdown-design.PNG

or when the object is rendered?

dropdown-preview.PNG

Steve

Avatar

Level 2

It happens in both design and rendered view.  It is a minor aesthetic problem, as the arrow obscures a sliver of the right hand edge of the last character in the text.  I tried the old ALT-255 trick, which inserted what looked like a blank in design view, but it disappeared in the rendered view.

I can live with this, but it would make my form a little nicer if I could "scootch" the text left a little.

Thanks for taking the time to respond.

Darrell

Avatar

Correct answer by
Former Community Member

Interesting. While the "marginRight" attribute does not exist for a dropdown list object "para" node, you can set the "marginRight" attribute. Try this...

// form1.page1.subform1.DropDownList1::initialize - (JavaScript, client)

DropDownList1.para.marginRight = "5pt";

Steve

Avatar

Level 2

Thanks, Steve. That worked. Sorry about the delayed gratitude, but I got

shunted off to a different project for a while, and haven't been checking

this email account.

Avatar

Level 3

The same thing happens with a text field whose caption is right justified.  It's too far to the right and squished right up next to the beginning of the field.

textField.jpg

I don't want to change the caption programmatically.  Rather, I'd like to be able to get a teensy weensy space at the end somehow, but it doesn't seem to take.  Any suggestions?

Thanks,

Elaine

Avatar

Former Community Member

If you hover over the little orange bar your cursor will change. Once it has changed you can slide the divider to the right to give you as much space as you need.

Paul

Avatar

Level 3

Thanks Paul, but the caption text scoots right along next to the orange bar

as you slide it. So that does not seem to work.

Avatar

Level 2

In this case, I find that inserting an ALT-255 character does add some space, even in the rendered view.  I don't know what is going on in the black box, but it does add a little space.  At the end of your caption, hold down the Alt key, and press 255 on your number keypad.

Darrell

Avatar

Level 4

Thanks Darrell, but that doesn't seem to work either. You can't see the

space in design or preview mode. --Elaine

Avatar

Former Community Member

In the Paragraph palette, make sure that you are editing the caption only, then set a right index to move the text slightly left.

screen1.jpg

Paul

Avatar

Former Community Member

On the Paragraph tab ....set it to adjust caption only then you can use the right index to set a small space to be used.

Paul

Avatar

Level 3

Yeah, baby! That did it! Thanks Paul! You have a fun job

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] ----