Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
Bert_Bimmel
in reply to: Bert_Bimmel

And what about that transience-flag that you can set for a custom browser?

 

  • You cannot declare a custom browser as transient upon creation. This flag can only be raised after creating, and thus dirtying the document
  • No matter if the flag is set or not, subsequent changes of the browsertree will not dirty the document. if you want your browsertree beeing saved with your file, you'll have to perform any random other action to dirty the file. if you don't, the browser will still be there after saving, closing and reopening the document, but it's entire content (except for it's root node) has gone down the drain
  • when the flag is set, the browser, whose initial creation did dirty the document, will be completely purged from the file when it's saved, closed and reopened

How is this supposed to make any sense???