Your achievements

0% to

Tip / to gain points, level up, and earn exciting badges like the new

Adobe LiveCycle (Archived)

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.

Read More & Register today!

SOLVED

How do you add pop up definitions to form fields in LiveCycle?

I've been trying to find information on adding a pop up definition to a LiveCycle pdf. I want users to be able to move their cursor over form field such as a text field or other field and have a definition pop up of what we want to see in the text field. I saw an example of this on a PDF, and it is helpful.

Has anyone done this before and could share useful tips/information? Thanks.

1.6K

3

1 Accepted Solution

Correct answer by

Use the Accessibility tool tip property.

Steve

View solution in original post

430

0

Jump to reply

3 Replies

Correct answer by

Use the Accessibility tool tip property.

Steve

431

0

Jump to reply

Just curious - would it matter if we chose, Screen Reader Precedence: Tool Tip, instead of "Custom Text"?

435

0

There are dependencies based upon the use of a screen-reader. See http://help.adobe.com/en_US/livecycle/9.0/designerHelp/000615.html

Steve

445

0

Related Conversations

need phone number box to disappear after phone number is entered correctly Solved

Solved

1.5K

0

2

My data source works in Preview PDF mode but not when I generate the form Solved

Solved

2.3K

0

2

Unable to save if a check box it is not checked Solved

Solved

2.3K

0

5

Floating field with pagenumbers in a fragment is messing up when used in masterpages Solved

Solved

1.4K

0

2

Need phone number box to disappear after phone number is entered correctly

12.5K

0

6

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