Stefan Cameron on Forms
Building intelligent forms using Adobe LiveCycle Designer

Bug List

The following table outlines bugs that have been found either in Designer (on any topic) or Acrobat (related to XFA/PDF forms). Please keep in mind that I’m providing this list and maintaining it for information purposes only. Whether a known bug gets fixed or not in a future release is something I cannot promise nor comment on. I will, however, make as much information available about the status of each bug as possible. Hopefully this will help you to determine if the brick wall you’re banging your head against is really a brick wall or not and whether there’s a work-around you can use in the interim.

Bug App Ver Fix
Cannot Override Calculations A/R 7.x 8.0
“Page n of m” Custom Object Broken in Tables Des 7.1 –
Image Field Z-Order Problems A/R 7.x X
Adding/Removing Table Columns A/R 7.05+ 8.0
Unable to Set Caption or Value Font Separately Des 7.0 7.1
Images not always embedded into PDFs A/R 8.0 8.1
Sending WSDL request using repeatable section A/R 8.0 8.1
Web service data not cleared on exception A/R 8.0 –
Table columns rendered incorrectly with new column width A/R 7.0.9+ 8.1
Cannot make a radio button list be “required” A/R 6.0.2+ 8.0
Field set to mandatory in list box Change event always set to mandatory A/R 7.0.9+ 8.1
List box with Change event script will not retain new selection value A/R 7.0.9+ 8.1
Cannot clear radio button list selection A/R 7.0+ –
Click and MouseUp events don’t fire after sign a digital signature field (this may be in older versions of A/R although I haven’t verified it) A/R 9.0- –

Legend

  • App: The application affected by the bug.
  • Ver: The version(s) affected by the bug. A negative sign (-) following a version number indicates that version and all earlier versions. Note that the bug may occur in earlier versions than that which is indicated as I’m not able to test in all released versions.
  • Fix: The version as of which the bug is fixed.
    • Nx: Indicates the bug has been fixed in the next release.
    • X: Indicates the issue isn’t really a bug (but may be perceived as one).

Reporting Bugs

The best way to report a bug to Adobe is to use the Bug Report Form. Choose Designer as the “Product name” to report LiveCycle Designer-related bugs.

I would also encourage you to post your observations here for the benefit of others. If you do, please indicate the version of the application which you believe to be affected, steps to reproduce it and a work-around, if you know of one.

Comments

If you wish to comment on a specific bug, please do so on the specific bug’s post.

Updated: November 5, 2008

Posted by Stefan Cameron on April 22nd, 2007
You can skip to the end and leave a response. Pinging is currently not allowed.

11 Responses to “Bug List”

  1. Gretchen on May 28th, 2008

    Stefan - Wondering if you’ve heard of this problem and know of a fix….
    When I open/use my Designer, my screen does this fade-in/fade-out loading thing. It does this for any step and change that I make - going from my Design view tab to my PDF Preview tab….just about anything I do, it seems to “refresh” the screen in this slow-fading way. It’s EXTREMELY time consuming and slows up my work. I’ve looked online and in the forums for a solution but can’t figure it out. What’s the deal??

  2. Stefan Cameron on May 28th, 2008

    Gretchen,

    It sounds like you’re running into performance problems on your system with respect to a new feature/effect that was added to Designer 8 which is to fade-in/out changes to the canvas area. Unfortunately, there is no way to turn this feature on/off. If you have a lot of other applications running at the same time, perhaps things would go a little smoother if you closed a few of them.

  3. superstator on July 14th, 2008

    I have the same issue. It is not a system performance problem - everything else runs fine and snappily. My machine happily runs multiple instances of Visual Studio 2008 / 2005, SQL Server test instances, VM’s and misc apps all together. LiveCycle cannot competently draw it’s cute fade-in/out running all by itself. Maybe it doesn’t like my video driver, but everything else does fine and all I want to do is turn the stupid effect off and get back to work.

  4. Eric Horde on August 25th, 2008

    Bug??

    I have a working PDF form that was created in Adobe and Designer
    (Livecycle). I needed to add (import) 5 pages from another PDF into
    the form. I can import while in Adobe Acrobat Pro and the new pages
    display fine, including all the form fields, buttons, etc…

    However when I switch back to Designer to add database fields to the
    newly added pages, the pages are missing/do not display.

    I open the form back up in Adobe acrobat Pro and the new pages are
    there.

    I have 36 pages visible in Acrobat Pro but when I switch to Designer,
    only 31 display. The new ones are not there.

    Any thoughts? Why can’t I see the new pages in Designer?

  5. Stefan Cameron on August 27th, 2008

    Eric Horde,

    I don’t think this is a bug. Please see my response to your comment on my Shading the caption, not the entire field article.

  6. Brian on September 15th, 2008

    Hi Stefan,

    I’d like to inquire with you regarding a possible bug with fragments. You can find a running thread of this at: http://www.adobeforums.com/webx/.59b66be7/0.

    What we’re seeing is that Designer is adding local overrides into our fragment instances ( found in the XML source code ) that are repositioning fields within the fragments when the form renders. Even when editing the XML directly, the tool seems to add the code right back in whenever the form is saved or previewed (i.e., whenever the XML Source editor palette is closed).

    Any help you can provide on the matter would be greatly appreciated.

    Thanks,
    Brian

  7. Stefan Cameron on September 20th, 2008

    Brian,

    This is a known bug in Designer 8.1 and should be fixed in Designer 8.2 (now released). It seems that it’s caused by the presence of text objects (a type of XFA node) in the referenced fragment. If such a node exists, some of the first-level nodes inside the reference will become “defined” in the referencing form. The result is that the order of the nodes inside the fragment reference is changed in the referencing form.

    For example, if your fragment looks like this:

    <subform>
    <field name="field1"/>
    <draw name="text1"/>
    <field name="field2"/>
</subform>

    The node becomes defined in the referencing form and the fragment, from the referencing form, ends-up looking like this in the Hierarchy palette (the order on the Canvas may also change in the referenced fragment subform has a flowed layout):

    + subform
    - text1

    Unfortunately, the only workaround I know of is to edit the XML Source and specify all of the first-level nodes that appear in the referenced fragment so that the order remains the same as the original. After you’ve done that, the referenced fragment will look like this in Hierarchy palette:

    + subform
    - field1
    - text1
    - field2

    Because the nodes inside the referenced fragment are specified in the referencing form, Designer will allow you to select and edit them however make sure you don’t. Restrict your editing to the subform which is the fragment reference. Do not edit objects inside of it even if Designer now allows you to select them.

    PS: I’ve updating the Adobe Forum thread you referenced. Thanks for pointing it out!

  8. Tim Goodman on September 25th, 2008

    Hi Stefan,

    I just found this bug in Designer 8.2.1 with image fields - it does not occur in forms saved in Designer 8.1

    Here is what I reported on the Adobe Go/Wish site:

    ******BUG******
    This is a Bug with LiveCycle Designer v8.2.1

    ImageField Objects that are not visible during Document Rendering phases, cannot be made visible once rendered

    Steps to reproduce bug:
    1. Create a new LiveCycle form, add an ImageField, set presence to invisible
    2. Add a button, once clicked sets presence for the Image field to visible
    3. Run the form in Acrobat
    Results: Clicking the button does not make the image field visible
    Expected results: Clicking the button should make the image field visible.

    I have a sample form that demonstrates this that I can e-mail you.

    Thanks,
    Tim

  9. Tim Goodman on September 25th, 2008

    Also … On the Adobe go wish site (http://www.adobe.com/go/wish) there is not a specific product entry for LiveCycle Designer … there are options for Acrobat Pro OR “Designer”…

    Is the Go/Wish site the best way to report LC Designer Bugs? And if so, which product option should we use?

  10. Tim Goodman on September 27th, 2008

    Please ignore my previous posts … I developed a Dynamic form on a PC with 8.1, then set the Tab order on a PC with 8.2.1

    The default option to “Save As”, must have converted the form type from Dynamic to Static… Frustrating!

  11. Stefan Cameron on September 27th, 2008

    Tim Goodman,

    Thanks for letting me know you were able to resolve the issue. I agree: It’s way too easy to fall into the static vs dynamic PDF trap!

    As for reporting bugs, the Adobe “Wish” site is the best way to do so and you should choose “Designer” from the product list when reporting LiveCycle Designer bugs. We monitor bugs reported via that page. I’ve also updated this page to clarify this process.

Leave a Reply

If you're including scripts: To make sure your script and comment are properly interpreted, please make sure you replace any less-than ("<") characters with their character code equivalent: "&lt;" (without the quotes). Otherwise, your script and comment will inadvertently be cut short.