I am using Framemaker 2020, (16.0.1). Dita 1.3.
The following problem only happens occasionally, and I am not clear on the pattern of what causes it.
Occasionally, when I have a ditamap and dita file open and am trying to edit it, the following behaviour occurs, which slows down editing the dita file to a very frustrating level:
Thus, it appears that cursor movements in a dita file are sometimes affecting both the dita file and the ditamap.
Other interesting observations:
Possible underlying cause;
Thanks for the quick reply Pulkit. I will email you a video of the error.
Some further information - this error only happens if the ditamap was saved as a MIF 2020.
Further update on file formats affected. I have now encountered this bug both with MIF2020 ditamaps and XML type ditamaps. However, there is a difference. The MIF2020 filetype will save the the ditamap in an unhappy state so that when re-opened, the ditamap will still exhibit this buggy behaviour. However, I have now observed this buggy behaviour in a XML filetype. I am still uncertain of the exact reproduction steps to get this problem to occur, but the above steps of "minimizing nodes" appears to "fix" the problem (which is frustrating if you happen to have a lot of nodes expanded).