-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Bug] Clearing private tabs from notification closes the app #9100
Comments
…ation closes the app'
I would like to take a go on this |
The expected behaviour is that the private tabs are closed AND we are redirected to PB home screen right? This bug is highly connected with #8590 in the sense that there's one fix for both. There are two approaches that I can think of for the PB notification, one simpler than the other, and the difference is this: |
@BranescuMihai the expected behaviour is as follows. There are two situations when users can tap on the “Close private tabs” notification.
The only difference between the two scenarios is: if Firefox is in background, we keep it there – don’t reopen it. If Firefox is in foreground, we will show it again. Either way, the page that should be shown is not the PB Homescreen, but the normal Homescreen |
…earing private tabs from notification closes the app'
…ring private tabs from notification closes the app' (+ cleanup)
I realized that Bram is not available for Easter, so for now, I think since we have a patch, we can fix this particular bug according to what Bram suggested, and then later we can revisit whether #8590 is still important. I'll flag Bram for the case that we're not addressing here is the one where a user is using Private Mode from the Private Browsing shortcut, which we made as a "Focus replacement", in #8590. |
When you clicked it, it would send your task to recent apps, removed the intent extra that was triggering this
…ation closes the app'
…earing private tabs from notification closes the app'
…ring private tabs from notification closes the app' (+ cleanup)
When you clicked it, it would send your task to recent apps, removed the intent extra that was triggering this
…ation closes the app'
…earing private tabs from notification closes the app'
…ring private tabs from notification closes the app' (+ cleanup)
When you clicked it, it would send your task to recent apps, removed the intent extra that was triggering this
We redirect to private mode if the entry point is one of the private shortcuts. We redirect to normal mode if the entry point is any other
…ation closes the app'
…earing private tabs from notification closes the app'
…ring private tabs from notification closes the app' (+ cleanup)
…ation closes the app'
…earing private tabs from notification closes the app'
…ring private tabs from notification closes the app' (+ cleanup)
When you clicked it, it would send your task to recent apps, removed the intent extra that was triggering this
We redirect to private mode if the entry point is one of the private shortcuts. We redirect to normal mode if the entry point is any other
…ation closes the app'
…earing private tabs from notification closes the app'
…ring private tabs from notification closes the app' (+ cleanup)
When you clicked it, it would send your task to recent apps, removed the intent extra that was triggering this
We redirect to private mode if the entry point is one of the private shortcuts. We redirect to normal mode if the entry point is any other
…SessionObserver The observer was moved and is now bound to the activity and its context. If the activity is re-created we leak the observer and therefore the activity itself. With this we make sure to stop the observer and also don't use the activity context to begin with.
…SessionObserver The observer was moved and is now bound to the activity and its context. If the activity is re-created we leak the observer and therefore the activity itself. With this we make sure to stop the observer and also don't use the activity context to begin with.
…SessionObserver The observer was moved and is now bound to the activity and its context. If the activity is re-created we leak the observer and therefore the activity itself. With this we make sure to stop the observer and also don't use the activity context to begin with.
…SessionObserver The observer was moved and is now bound to the activity and its context. If the activity is re-created we leak the observer and therefore the activity itself. With this we make sure to stop the observer and also don't use the activity context to begin with.
…SessionObserver The observer was moved and is now bound to the activity and its context. If the activity is re-created we leak the observer and therefore the activity itself. With this we make sure to stop the observer and also don't use the activity context to begin with.
…SessionObserver The observer was moved and is now bound to the activity and its context. If the activity is re-created we leak the observer and therefore the activity itself. With this we make sure to stop the observer and also don't use the activity context to begin with.
…SessionObserver The observer was moved and is now bound to the activity and its context. If the activity is re-created we leak the observer and therefore the activity itself. With this we make sure to stop the observer and also don't use the activity context to begin with.
The observer was moved and is now bound to the activity and its context. If the activity is re-created we leak the observer and therefore the activity itself. With this we make sure to stop the observer and also don't use the activity context to begin with.
Steps to reproduce
Expected behavior
Private tabs are closed.
Actual behavior
App gets removed from recent apps.
Device information
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: