Closed
Bug 1328069
Opened 8 years ago
Closed 11 months ago
[e10s] Plugin notification appears in wrong tab
Categories
(Toolkit Graveyard :: Notifications and Alerts, defect)
Toolkit Graveyard
Notifications and Alerts
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: arni2033, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
(deleted),
application/zip
|
Details |
>>> My Info: Win7_64, Nightly 49, 32bit, ID 20160526082509 STR_1: 1. Download and extract "testcase 1" in a folder with short full file name 2. Open file "testcase 2016.05.29.html" in the browser 3. Click on the page from Step 2. 4. Reload the tab opened in Step 2 and perform Step 3 again. (Repeat this step once if there's no bug) AR: Plugin notification is displayed in urlbar in the tab opened in Step 3 ER: The tab opened in Step 3 is about:blank, so there should be no plugin notification displayed Notes: I first encountered this after pressing Ctrl+T. It's possible if there's a delay (between loading Flash and opening new tab) from 1ms to ~300ms when I set my laptop to "low performance", or delay 1-90ms when I set it to "high performance". Actually, it doesn't matter, because Flash can load at any time, right before user opens a new tab. Now that you know about this bug, please check other notifications in urlbar in e10s mode. This is regression from bug 1254104. Regression range: > https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=2fbf81b363ef3708e4e78bf26e998085a5f8e85b&tochange=4f18cd7a0bc81ce85d0668c86e66156455d9cb84@ Mike de Boer [:mikedeboer]: It seems that this is a regresion caused by your change. Please have a look.
@ Mike de Boer [:mikedeboer]: It seems that this is a regresion caused by your change. Please have a look.
Flags: needinfo?(mdeboer)
Comment hidden (spam) |
Component: Untriaged → Notifications and Alerts
Product: Firefox → Toolkit
Comment 3•8 years ago
|
||
Since we're not shipping Hello anymore, I think it's safe to just backout the offending changeset.
Flags: needinfo?(mdeboer)
Comment 4•8 years ago
|
||
However, since bug 1254104 backed it out already, what's left to do here?
Flags: needinfo?(arni2033)
I didn't know that you will back out the bug when I wrote this report (2016.05.28). Bugs were reported automatically. The only thing I can say is: I also don't know if this was backed out properly. If you (or somebody) can reproduce it on reported version, and can't reproduce it now, it's safe to close it. (bug 1315317 looks like duplicate of this)
Flags: needinfo?(arni2033)
Updated•2 years ago
|
Severity: normal → S3
Updated•11 months ago
|
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → INCOMPLETE
Updated•11 months ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•