web.telegram.org push notifications opened inconsistently

NEW
Unassigned

Status

()

defect
2 years ago
a month ago

People

(Reporter: marco, Unassigned)

Tracking

(Blocks 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

2 years ago
Alerts opened from web.telegram.org push notifications are shown on the top left corner of the screen (other push notifications are shown on the top right).
Also I noticed that when you click on them it open a new tab rather than the current tab open with Telegram.
Reporter

Updated

2 years ago
Component: Notifications and Alerts → DOM: Push Notifications
Product: Toolkit → Core
(In reply to Rémy Hubscher (:natim) from comment #1)
> Also I noticed that when you click on them it open a new tab rather than the
> current tab open with Telegram.

This can be due to the site's service worker script specifically choosing to do it.

It could also be a consequence of an issue with multi-e10s.

What config are you on?
More specifically, we need to know:

* desktop or mobile
* FF version number
* e10s configuration

If you post about:support output I think all of this will be in there.
- desktop Firefox 55.0 (nightly build)
- e10s activated.

Nom: Firefox
Version: 55.0a1
Identifiant de compilation: 20170531100318
Canal de mise à jour: nightly
Agent utilisateur: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0
Système d’exploitation: Linux 4.10.0-21-generic

Multi-process staged rollout	1.50	e10srollout@mozilla.org

Sorry my about:support is in French :(
Also I have to say my telegram is in a pin tab, which could also be the source of the problem.
Ok, the issue with opening in a new window is likely due to multi-e10s and not having bug 1293277 yet.  Once that is fixed the problem should be resolved.  Most likely in FF56.

Lets keep this bug for the notification placement issue described in comment 0.  That sounds different and unrelated.
Ok sorry about the noise thanks.
Reporter

Comment 8

2 years ago
(In reply to Ben Kelly [reviewing, but slowly][:bkelly] from comment #2)
> This can be due to the site's service worker script specifically choosing to
> do it.

In this case not, as you can't have two Telegram tabs open (Telegram will complain), so pretty sure they don't want to open a new tab.
(In reply to Ben Kelly [reviewing, but slowly][:bkelly] from comment #6)
> 
> Lets keep this bug for the notification placement issue described in comment
> 0.  That sounds different and unrelated.

In that case we should probably move the component. William, have you seen this before?
Component: DOM: Push Notifications → Notifications and Alerts
Flags: needinfo?(wchen)
Product: Core → Toolkit
Duplicate of this bug: 1410054
Flags: needinfo?(william)
You need to log in before you can comment on or make changes to this bug.