Firefox shows Certificate Confirmation Dialog on wrong workspace

Bug #18150 reported by Eric Feliksik on 2005-06-15
8
Affects Status Importance Assigned to Milestone
Mozilla Firefox
Invalid
Medium
firefox (Ubuntu)
Medium
Unassigned
firefox-3.0 (Ubuntu)
Medium
Unassigned

Bug Description

Do the following things:
1) Have some Firefox windows open on workspace 1
2) Make sure no firefox windows are open on workspace 2, and the firefox window
in workspace 1 is the last firefox window touched.
2) Click a https-link in Thunderbird on workspace 2.
3) Wait till the page is shown.

Buggy behaviour: A certificate question will be on workspace 1. It took me a
while to figure that one out!

Expected behaviour: A certificate question is shown on workspace 2, where the
new firefox window with the soon-to-be-shown content is.

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050524 Firefox/1.0 (Ubuntu package 1.0.2 MFSA2005-44)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050524 Firefox/1.0 (Ubuntu package 1.0.2 MFSA2005-44)

With firefox 1.0.2, when running a second firefox command, while there is an
instance displaying a browser window in a different workspace, firefox display
any certificate confirmation dialog on top of the previously existing browser
window.

With deerpark, a window is not even opened in the current workspace, instead a
new tab is created in the existing window.

Reproducible: Always

Steps to Reproduce:
1. start firefox 1.0.2 (see build identifier): "firefox" in the shell.
2. go to another workspace
3. open a url to a website whose certificate requires some sort of confirmation
(obsolete certificate, domain name mismatch, whatever), the provided URL work as
of today, but that it may get fixed. "firefox http://launchpad.ubuntu.com" in
the shell.

Actual Results:
The second firefox command causes the already running instance to display a new
browser window in the current workspace, but the certificate confirmation dialog
appears on top the previous window, in another workspace.

Expected Results:
The certificate confirmation dialog should appear on top of the newly created
window, which is the one the user is currently looking at.

Mozilla daily: "Mozilla 1.8b2 build 2005070205" produces the expected behaviour.

Firefox daily: The daily firefox "Mozilla Firefox 1.0+" (sorry, but that's the
output of firefox --version, the date is 2005-07-12) behaves still differently.
The second firefox command opens the specified url in the already existing
window, in a different workspace, producing no user-observable result at all in
the current workspace.

I'm not sure if I should file the behaviour of the current deerpark as another bug.

Seth Kinast (seth) wrote :

You're right, it should open the window/tab the certificate is coming from.

Alexandre Otto Strube (surak) wrote :

confirmed upstream. will add a watch to it.

Changed in firefox:
status: Unconfirmed → Confirmed
Changed in firefox:
status: Unconfirmed → Confirmed
Ian Jackson (ijackson) on 2006-09-27
Changed in firefox:
assignee: ijackson → nobody
David Farning (dfarning) on 2006-12-31
Changed in firefox:
assignee: nobody → mozillabugs
David Farning (dfarning) on 2007-02-24
Changed in firefox:
assignee: mozillateam → mozilla-bugs
Marco Rodrigues (gothicx) wrote :

Isn't this fixed on Firefox v2.x ?!

Alexander Sack (asac) wrote :

marco, can you confirm that this is fixed?

Alexander Sack (asac) wrote :

on track upstream => In Progress for Ubuntu task

Changed in firefox:
status: Confirmed → In Progress
Alexander Sack (asac) on 2008-10-31
Changed in firefox:
assignee: mozilla-bugs → nobody
status: In Progress → Triaged
Changed in firefox-3.0:
importance: Undecided → Medium
status: New → Triaged
Micah Gersten (micahg) wrote :

No more fixes will occur for Firefox 2.

Changed in firefox (Ubuntu):
status: Triaged → Won't Fix
John Vivirito (gnomefreak) wrote :

Sorry but Firefox-3.0 has reached EOL and will not get this fix or any other updates. Please try to confirm this happens with latest stable release of Firefox-3.5 from our repos.

affects: firefox-3.0 (Ubuntu) → firefox-3.5 (Ubuntu)
John Vivirito (gnomefreak) wrote :

They have decided to release 3.0.18 as of yesterday

affects: firefox (Ubuntu) → firefox-3.0 (Ubuntu)
Changed in firefox-3.0 (Ubuntu):
status: Won't Fix → Triaged
Changed in firefox:
importance: Unknown → Medium

Does this still happen with the newest Mozilla products? Thank you!

Changed in firefox-3.0 (Ubuntu):
status: Triaged → Invalid
affects: firefox-3.5 (Ubuntu) → firefox (Ubuntu)
Changed in firefox (Ubuntu):
status: Triaged → Incomplete
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Changed in firefox (Ubuntu):
status: Incomplete → Confirmed
Changed in firefox:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.