[KULRICE-12505] JS Error with session storage when using Safari in private browsing mode Created: 15/Apr/14 Updated: 16/Jan/15
|Project:||Kuali Rice Development|
|Component/s:||Development, User Experience (UX)|
|Security Level:||Public (Public: Anyone can view)|
|Reporter:||Adam Campbell (Inactive)||Assignee:||Martin Taylor (Inactive)|
|Remaining Estimate:||0 minutes|
|Time Spent:||4 hours|
|Original Estimate:||0 minutes|
|Sprint:||2.4.0-rc1 Sprint 8|
|KAI Review Status:||Not Required|
|KTI Review Status:||Not Required|
|Code Review Status:||Not Required|
|Include in Release Notes?:||
When using Safari 7.0.3 in private browsing mode the following error appears:
This is caused by lack of support for session storage in Safari 7 private browsing. Fix the check to note session storage is not supported and confirm no sporadic issues with undefined obj.length or data.warnings.length.
|Comment by Martin Taylor (Inactive) [ 15/Apr/14 ]|
to help track session support more accurately in safari (stored return value once so it could be reused) but I get several new errors in chrome private browsing unrelated to session storage.
|Comment by Martin Taylor (Inactive) [ 16/Apr/14 ]|
When testing session storage check, found that an Error is then thrown during setupPage() which prevents features such as actionsDefaults to be set (this can cause errors with functionality such as login/etc...). Since sessionStorage's issue is at the modification of a row (remove or setting), limited the support check to these. For reading (which happens in setupPage), I left it to check on sessionStorage alone. Read on session storage will not cause an error and simply return null which does not cause the page to fail to setup.