Project

General

Profile

Actions

Feature #92155

closed

Browser Notifictaions in the Backend

Added by Katharina Strasser over 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2020-09-02
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Hello

in the LoginRefreh.js of the Backend is a 'Notification.requestPermission()' this leads into a Permission request.

Is it possible to disable this permission request?

We have 500+ Typo3 Instances running and our editors does not want such messages.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #90666: Firefox blocks request for native browser notification permissionsClosedFrank Nägler2020-03-06

Actions
Related to TYPO3 Core - Task #92988: Remove browser-native Notification APIClosedBenni Mack2020-12-04

Actions
Actions #1

Updated by Chris topher over 3 years ago

  • Project changed from 9 to TYPO3 Core
Actions #2

Updated by Georg Ringer over 3 years ago

  • Related to Bug #90666: Firefox blocks request for native browser notification permissions added
Actions #3

Updated by Georg Ringer over 3 years ago

  • Status changed from New to Needs Feedback

thanks for creating this issue. TYPO3 uses this notifications currently only for notifications if the login session will expire. IMO this information is important for the editors but it is also ok to disable it.

what is the exact problem your editors have with such information?

Actions #4

Updated by Katharina Strasser over 3 years ago

Georg Ringer wrote:

thanks for creating this issue. TYPO3 uses this notifications currently only for notifications if the login session will expire. IMO this information is important for the editors but it is also ok to disable it.

what is the exact problem your editors have with such information?

There no real problem with this, our editors just don't want to do another click or sometimes they getting confused by the message after the login. So I investigated what caused the messsage.

Actions #5

Updated by Oliver Bartsch almost 3 years ago

  • Status changed from Needs Feedback to Closed

Hi, the notification API was completely removed again in #92988. I'll therefore close this issue since there are no further tasks to do. In case you think there is still something to improve, please get in touch with me directly or just create a new issue, referencing this one.

Actions #6

Updated by Oliver Bartsch almost 3 years ago

  • Related to Task #92988: Remove browser-native Notification API added
Actions

Also available in: Atom PDF