noChrome breaks Adobe Sign

[Cameron5FBC]

If you use the "noChrome" flag in the Adobe Sign API to open up a window, then it breaks the Adobe Sign UI for any sessions, which completely breaks Adobe Sign's dashboard for regular use, and there's no recovering or logging out without clearing session.

Easiest steps to reproduce (in the examples, I'll be using the base URL that I'm redirected to after signing in to Adobe Sign, but you would replace it with yours):

Go to https://graphite.na4.adobesign.com/public/compose?noChrome=true

Try to go back to home: https://graphite.na4.adobesign.com/ (it will redirect you to https://graphite.na4.adobesign.com/account/homeJS). The page will be blank.

You are unable to navigate to other pages or sign out without clearning your browser's cache/session/local storage.

[Cameron5FBC]

To be clear, what I would expect to happen is that you can still use Adobe Sign. That is, it can differentiate when the URL has "noChrome=true" in it and only removes the chrome (menu bar, etc) from the popup windows and not make a permanent change. We have customers that have used our integration and then thought Adobe Sign was forever broken.