1943218 - Tapping on push notifications opens a new about:blank page

Status: RESOLVED DUPLICATE of bug 1825910

(Fenix :: Push, defect)

Description

[aaruti]

Attachment: Push notification open blank screen.mp4

134.0.2 (Build #2016068999), hg-33bb8362cc38+
GV: 134.0.2-20250120135430

Steps to reproduce:

I click the push notifications, instead of opening the webpage it is opening a new tab with about:blank in the address bar (blank page)

Trigger push notification from here.
https://pushpad.xyz/demo

Actual results:

Opened a blanked page

Expected results:

Should open the respective site

Comment 1

[aaruti]

Attachment: Screenshot_2025-01-23-06-48-39-30_3aea4af51f236e4932235fdada7d1643.jpg

Comment 2

[aaruti]

Device : OnePlus 12
Android V: Android 15

Comment 3

[Andrew McCreight [:mccr8]]

That looks like an annoying bug, but what is the security issue here? Thanks.

Comment 4

[aaruti]

Apologies. It's not related to security. Issue is when I click push notification it open blank screen with about:blank at the address bar.
I am trying this on Firefox main. In beta and nightly don't see this issue

Comment 5

[Kagami Rosylight [:saschanaz] (they/them)]

This is supposed to be fixed by bug 1825910 and I cannot reproduce this. pushpad.xyz is the exact website that was raised there. Maybe either Mira or :arai can check again too?

Comment 6

[Andrew McCreight [:mccr8]]

It looks like bug 1825910 wasn't fix in 134, so I think this is expected and we could dupe it over there. The reporter said that beta and Nightly aren't affected (thank you for checking!).

Comment 7

[Kagami Rosylight [:saschanaz] (they/them)]

Ah, I missed comment #4. Agreed that this should be a dupe, but I'm not the component owner so I defer that to :arai.

Comment 9

[aaruti]

Dear team,

I could see that my ticket was closed as a duplicate and is being tracked under another existing bug. However, it has been more than two years, and the issue remains unresolved with no significant updates provided.

This delay has caused ongoing challenges, and I kindly request your support in prioritizing this matter. I would greatly appreciate any insights on the current status and an estimated timeline for resolution.

Please assist in addressing this at the earliest convenience.

Comment 10

[aaruti]

I could also see this bug is also marked closed.

Comment 11

[Kagami Rosylight [:saschanaz] (they/them)]

Hello aaruti,

First, sorry for the long inconvenience. We acknowledge that this took more time than people would have expected.

We are happy to report that this is fixed in Firefox 135 (which is now in beta) and will be available on Firefox stable 12 days later (please refer to https://whattrainisitnow.com/ on that matter).

Please feel free to provide more feedback about this when Firefox 135 ships.

Comment 12

[aaruti]

Thank you