Description Anamaria Pradais 2014-09-23 10:09:39 EDT

Assume the scenario:
An user of our application can access a page and login. Only one login session is allowed at a time. If the user closes the browser, presses f5, navigates to another url or closes the current browser tab, an UISessionEvent is issued (and the user is logged out). In this way if he returns to the login page a new login is possible.

I have noticed different behavior in these two similar situations using iPad:

Normal browser mode:
1. Open url and login.
2. Press home button - sends browser to background. No session UISessionEvent is sent so I assume the session is still active.
3. Open task manager and open the already running browser instance. Session is active and all works fine.

Full screen mode:
1. Open url and login.
2. Press home button - sends app to background. No session UISessionEvent is sent so the session appears to still be active.
3. Open task manager and open the already running full-screen app instance. Session is somehow not active. No session UISessionEvent was ever sent to the server. Our user lands back in the Login window (and cannot login again because the UISessionEvent was not issued). 

I have encountered this issue in version 2.2 and since I could not find any similar bug report I might assume is still is a bug in next version (2.3 ?).