Console for a single pane
Devtools extensions do not work in this mode.
Content security policies (CSP)
Legacy mode does not adhere to Content Security Policies and is therefore not recommended to be used for regular web browsing.
document.domain can not be set
Legacy mode can not show any page that tries to set document.domain.
SSO/oAuth/redirecting logins do not always work correctly
SSO and oAuth logins like those of Google or Microsoft don't always work correctly in Legacy mode. Switching to the default mode and using full browser mode or focus mode usually works in these situations. After you've done this, the session will be shared with all panes so you can switch back to multiple panels and turn Legacy mode on again. You'll be logged in on all panes.
An easy way is to use the side browser to log in.
Polypane will show a popup if it detects an SSO login in Legacy mode and suggest to do this for you.
Because all panes share a session, you will be logged in in all of them.
Frameworks with CSRF protection
Because Legacy Mode shows a site in multiple panes in a shared context, any framework that uses unique tokens per request is going to have an issue dealing with multiple panes with different tokens. This means for example that frameworks like Django, Ruby on Rails or Laravel will give an error in Polypane. Django and Ruby on Rails will give you a CSRF token error and Laravel will return a 419 error. Polypane will show a popup if it detects a CSRF token on the page.
Switching to the default mode and using full browser mode or focus mode usually works in these situations. After you've done this, the session will be shared with all panes so you can switch back to multiple panels and turn Legacy mode on again. You'll be logged in on all panes.
window.open) are disabled in this mode.
Is your question not answered?
Ask via Twitter, Slack or our contact form