command w on Mac does not close single tab - closes all tabs - in facebook

RESOLVED INCOMPLETE

Status

Camino Graveyard
Tabbed Browsing
RESOLVED INCOMPLETE
7 years ago
7 years ago

People

(Reporter: mjb, Unassigned)

Tracking

Details

(Whiteboard: [CLOSEME 01/15], URL)

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.0.19) Gecko/2010111021 Camino/2.0.6 (like Firefox/3.0.19)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.0.19) Gecko/2010111021 Camino/2.0.6 (like Firefox/3.0.19)

In Facebook I open a number of links into separate tabs. When I use command 'w' to close the tab, it closes all tabs, including the main window. 

In addition, render issues are present. When I navigate to an open tab, the page is blank until I refresh the page. 

Reproducible: Always

Steps to Reproduce:
1. Open tab
2. Use command 'w' (Mac) to close tab
3. All tabs and window closed.
Actual Results:  
Same same

Expected Results:  
Closed a single tab. 

New consequence after updating from 2.0.5 to 2.0.6
Using default theme. Mac OS X 10.6.5 - Macbook Pro

Comment 1

7 years ago
What happens if you try this with a default profile? Troubleshoot Camino can automate this for you.

http://pimpmycamino.com/parts/troubleshoot-camino

If the issue is still present with Troubleshoot Camino, can you verify that it (still) works with Camino 2.0.5?

http://caminobrowser.org/releases/2.0.5/

Comment 2

7 years ago
This sounds a lot like the old (and fixed) bug 432983.

Can you reproduce this on any sites besides Facebook, or can you give us a *specific* URL that you have open in the foreground when this happens?

Comment 3

7 years ago
Can you please answer the questions in comment 1 and comment 2?
Whiteboard: [CLOSEME 01/15]

Comment 4

7 years ago
INCOMPLETE absent answers to the pending questions.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
(Reporter)

Comment 5

7 years ago
Hi there. This stopped happening on its own. No idea why.
You need to log in before you can comment on or make changes to this bug.