Russell Solowoniuk <email@example.com> wrote:
Maybe Adobe fixed it in one of their updates, as FS said it wasn’tTo be fair to the technical support person, if it wasn't their bug but
Adobe's, then there might not have been any other practical work-around until
Adobe fixed it in an update. "Just don't do the action that triggers the bug
until it's fixed" seems to me to be good advice.