I'm concerned about multiple tabs opened with different connections. The sessionStorage is shared by all tabs connected to the same server. So for me, the session should be stored per user/database.
> I'm concerned about multiple tabs opened with different connections. The sessionStorage is shared by all tabs connected to the same server. So for me, the session should be stored per user/database.
You don't have to worry. SessionStorage is not shared between tabs. See first paragraf of:
Then will it not better to store for a longer time the session. This sessionStorage implementation will not allow to open multiple tabs nor support URL schema.
I don't think we should auto-login for multiple tabs (as multiple tabs is the same as multiple instances of the tryton client). Otherwise is not possible to work on different companies with the same user and navigator, which is currently possible by using different tabs.
On 2018-01-29 16:10, Sergi Almacellas Abellana wrote:
> I don't think we should auto-login for multiple tabs (as multiple tabs is the same as multiple instances of the tryton client). Otherwise is not possible to work on different companies with the same user and navigator, which is currently possible by using different tabs.
I do not see why it would not be possible. The context will not be
stored nor shared.
Also I do not think you should compare tabs of browser to instances of
desktop. They are different and we do not need to share a common
behaviour.
Ok, so I updated the review to store on localstorage, which allow to open multiple tabs on the same server (which is detected by the window.location) without repeating the credentials
On 2018-01-29 17:34, Sergi Almacellas Abellana wrote:
> Ok, so I updated the review to store on localstorage, which allow to open multiple tabs on the same server (which is detected by the window.location) without repeating the credentials
window.location is not enough. It depends also on the database.