Project

General

Profile

Actions

Task #81156

closed

Safari on Mac in incognito mode > Backend tabs not working

Added by Riccardo De Contardi over 7 years ago. Updated almost 7 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
Category:
Backend JavaScript
Target version:
-
Start date:
2017-05-05
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Sprint Focus:

Description

Steps to reproduce:

1) open Safari window in incognito mode (privage browsing)
2) open the TYPO3 backend
3) edit a page
4) click on a tab

Result: not working

Javascript error:

[Error] QuotaExceededError (DOM Exception 22): The quota has been exceeded.
    setItem (Tabs.js:57)
    storeActiveTab (Tabs.js:57)
    (funzione anonima) (Tabs.js:82)
    dispatch (jquery-3.2.1.min-2c4cb0f1e959a187919f13035a2bc894.js:3:10322)
    trigger (jquery-3.2.1.min-2c4cb0f1e959a187919f13035a2bc894.js:4:5634)
    (funzione anonima) (jquery-3.2.1.min-2c4cb0f1e959a187919f13035a2bc894.js:4:6146)
    each (jquery-3.2.1.min-2c4cb0f1e959a187919f13035a2bc894.js:2:2720)
    show (bootstrap.js:24:1253)
    (funzione anonima) (bootstrap.js:24:818)
    each (jquery-3.2.1.min-2c4cb0f1e959a187919f13035a2bc894.js:2:2720)
    e (bootstrap.js:24:2335)
    dispatch (jquery-3.2.1.min-2c4cb0f1e959a187919f13035a2bc894.js:3:10322)

Tested with both 7.6.16 and 8.7.1

Actions #1

Updated by Mona Muzaffar over 7 years ago

seems to be a design problem of safari in incognito mode.
(found some discussion on this topic here: https://github.com/marcuswestin/store.js/issues/42 -
'When Safari (OS X or iOS) is in private browsing mode, it appears as though localStorage is available, but trying to call .setItem throws an exception')
So safari forbids websites from writing a file locally in incognito mode.

A solution might be to catch the exception and give the user a warning instead, that he should change the browser mode or browser...

Actions #2

Updated by Mona Muzaffar over 7 years ago

  • Tracker changed from Bug to Task

This is not really a core bug but more of a task to give the user a proper warning/alert

Actions #3

Updated by Frank Nägler about 7 years ago

  • Status changed from New to Accepted

agree, we can and should catch this exception and show warning. maybe we could add a global check (e.g. try to write to localStorage) and if the check fail, show a Notification.

Actions #4

Updated by Frank Nägler almost 7 years ago

it looks like it is fixes since Safari 11, can anyone confirm that this bug is fixed in Safari 11 and still available in Safari 10?

Actions #5

Updated by Gerrit Code Review almost 7 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54764

Actions #6

Updated by Riccardo De Contardi almost 7 years ago

I can confirm that it is fixed for Safari 11. Cannot reproduce it with the description I wrote on the issue. Tested with 7.6.23, 8.7.8, 9.0.0-dev (latest master)

Actions #7

Updated by Frank Nägler almost 7 years ago

  • Assignee set to Frank Nägler

Thank you for the feedback, we need a system with safari 10 on os x to test the patch.

Actions #8

Updated by Frank Nägler almost 7 years ago

  • Status changed from Under Review to Rejected

we will reject this issue, because affected safari verison is very old

Actions

Also available in: Atom PDF