Expand my Community achievements bar.

SOLVED

Reader versus Browser

Avatar

Level 3

I have designed a LC form (with lots of JavaScript code).

I just realized that the form can be viewed and completed within a browser or the Acrobat Reader.

Since I have done all my testing with the Reader, my question is, "Can I expect the form to function the same, within a browser?"

I'm assuming the principle browsers like Explorer, Safari, and Firefox -- at their latest versions.

Thank you for all feedback.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Yes.

Keep in mind that PDF uses its own JavaScript engine. There may some fringe cases IF you are performing operations that involve the browser plug-in or ActiveX Control. Perhaps you should ask yourself if the script uses any functionality that is not backward compatible in Reader. In other words, will the form behave the same in Reader 5 and Reader 9.

View solution in original post

3 Replies

Avatar

Level 3

I love that answer -- short, and to the point.

I half expected that I might get a few "you need to watch it" or "consider that."

Is there any "advise" within this context?

Avatar

Correct answer by
Former Community Member

Yes.

Keep in mind that PDF uses its own JavaScript engine. There may some fringe cases IF you are performing operations that involve the browser plug-in or ActiveX Control. Perhaps you should ask yourself if the script uses any functionality that is not backward compatible in Reader. In other words, will the form behave the same in Reader 5 and Reader 9.

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