Acrobat 8 backward compatibility issues?

[Former Community Member]

Hi,



after reading two postings in this forum, I worry about backwards compatibility of Acrobat (and Reader) 8 with LiveCycle 7 forms.



Does anyone know of some Acrobat 8 release notes, which tell what features of LiveCycle won't work in Acrobat 8 (if any)?



Over here,
adobeforums.com user Dan Kilty states, that he's concerned about data bindings and signature compati...:

> Problem 2: With the form open in Adobe Designer 8, for all radio buttons

> in a form (with a schema associated) originally created in Designer 7.0,

> the environment displays that the radio buttons have "Normal data binding

> and may have undesirable results when a default data connection is defined



Also,
Stefan of Adobe kind of confirmed, that accessing dropdowns may not be fully backwards compatible:

> It looks like Acrobat 8.0 broke something that prevents my sample form

> from working correctly. It has to do with the call to

> resolveNodes("#items[*]")



So what's going on with Arobat 8 backwards compatibility?

Is there some kind of list to specify, which (Javascript LC 7) properties won't work in Acrobat 8?

Do I even have to be concerned?



Regards,

Steve

[Former Community Member]

We have a document posted at http://www.adobe.com/devnet/livecycle/articles/designer8_lc72.html that describes how Designer 8 should work with LiveCycle 7. Anything not in this document should be thought of as a bug and should be reported here: http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform



With that said, we will change JavaScript behavior that we determine to be security risks.



Thanks,

Mark