Skip to main content
C
cheryls1730789
Known Participant
June 7, 2021
Question

Bug 9622: Trying to get this fixed

  • June 7, 2021
  • 2 replies
  • 351 views

In May I posted the following concerning bug 9622:

 

I entered a bug for Framemaker 2020 back in January in Adobe's tracker tool (bug  9622). It had to do with the following conditional tags being added to the product by default:

FM_PDF_Comments_Highlight

FM_PDF_Comments_Underline

5 others also requested that the bug be fixed also. However, it is now May and it is still Open, not fixed. I have been waiting for this fix so i can upgrade Framemaker where i work to Framemaker 2020. We use conditional text heavily here and won't go to FM 2020 until this bug is fixed. How do we get Adobe to fix this bug?  Does anyone have any ideas?

 

Since that time I have been monitoring the bug. The status went from "Open" to "To Track" to "In Development" back to "To Track" back to "Open". No explanation in my original post as to why it is not being fixed. So I am concerned the bug I found will never get fixed. So I am posting again in the hope this will be fixed or at least I will get an explanation as to why it will never get fixed. 

 

Note: Since that time one other person also requested that it be fixed so now we are up to 7 requests.

 

Thank you to all for reading this.

    This topic has been closed for replies.

    2 replies

    S
    Community Manager
    Stefan GentzCommunity Manager
    Community Manager
    June 7, 2021

    Unfortunately changing the default visibility of these two conditionals in the conditional tags panel did not make it into Update 2.

    It is currently scheduled for Update 3.

    We understand that showing these conditionals by default in the conditional tag panel is causing an inconvenience and will improve this.

      C
      cheryls1730789Author
      Known Participant
      June 7, 2021

      Thank you for your update.

       

      LinSims
      Community Expert
      LinSimsCommunity Expert
      Community Expert
      June 7, 2021

      It certainly isn't fixed in the update that dropped last week, which is annoying.

       

      Technically, those conditions existed all along, since they're used with FrameMaker's track changes feature. But they shouldn't be showing up in the pod unless you're actually using that feature. <grumpy>

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices