Closed Bug 357417 Opened 18 years ago Closed 18 years ago

Cannot Open Link In New Tab via Contextual Menu (Ctrl+click a link in OS X)

Categories

(SeaMonkey :: UI Design, defect)

PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: robrackn, Assigned: jag+mozilla)

References

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20061020 SeaMonkey/1.5a
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20061020 SeaMonkey/1.5a

Control + Clicking an active link will quickly pop up the contextual menu offering options to open link in new window, or new tab, etc.

Problem is, the contextual menu doesn't stay open long enough to do anything. In every case, the only thing that happens is the link is opened in a new window.

Trunk Build October 20, 2006

In this same contextual menu are items such as:
Bookmark Link, Save Link Target, Copy Link Location, Bookmark this page, send page, etc.

The problem seems to obly happen with links. When in control+click on images or the background, the respective contextual menu stays open and allows me to select an item.

Reproducible: Always

Steps to Reproduce:
1. Go to a page with a link.
2. Ctrl+click (mac) to bring up the contextual menu to open link in new window, or open link in new tab.


Actual Results:  
The contextual menu quickly goes away before being able to select anything, and then the link opens up in a new window.

Expected Results:  
It should work as before. The contextual menu would stay open long enough for the user to choose if they want to open link in new window, or new tab, or bookmark the page, or send the page, or etc.
Version: unspecified → Trunk
Hmm, did this broke between September 28/29?
(In reply to comment #1)
> Hmm, did this broke between September 28/29?
> 

No. 
I just tried Sep 28 and Sep 29 builds. 
The contextual menu works correctly in both of the builds. 
seamonkey-1.0.5.en-US.mac.dmg       28-Sep-2006 22:50
seamonkey-1.1b.en-US.mac.dmg        29-Sep-2006 21:08
(In reply to comment #2)
> (In reply to comment #1)
> > Hmm, did this broke between September 28/29?
> > 
> 
> No. 
> I just tried Sep 28 and Sep 29 builds. 
> The contextual menu works correctly in both of the builds. 
> seamonkey-1.0.5.en-US.mac.dmg       28-Sep-2006 22:50
> seamonkey-1.1b.en-US.mac.dmg        29-Sep-2006 21:08
> 

Sorry for any misunderstanding here, but I was talking about trunk (I ment that in my comment in bug 357415 as well). The switch to cocoa toolkit happened after the September 28 trunk build was made, but before the  September 29 trunk build was made. I was curious to see if that might have caused the issue you see. I was actually refering to those two builds:

http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2006-09-28-06-trunk/
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2006-09-29-06-trunk/

There are actually builds from 3 different code branches available:

Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
rv:1.9a1) Gecko/20061020 SeaMonkey/1.5a
 = A trunk build from the code branch where all the major development occurs. This is where you do all the risky and big changes (this is why the builds sometimes are almost broken). This is the code that the forthcoming seamonkey 1.5 release will be built from (same core code-base that Firefox 3 will be built upon - the 1.9 Gecko branch).

seamonkey-1.0.5.en-US.mac.dmg       28-Sep-2006 22:50
 = A build from the stable 1.8.0.x branch (a release build, I guess). On this code branch nothing really changes that much - only security fixes goes in here.

seamonkey-1.1b.en-US.mac.dmg        29-Sep-2006 21:08
 = A build from the 1.8 branch (this is the branch that the 1.1 release will be made from). On this branch some "lighter" development is taken place - not too risky features might be added etc etc.





 
(In reply to comment #3)
...I was talking about trunk (I ment that
> in my comment in bug 357415 as well). The switch to cocoa toolkit happened
> after the September 28 trunk build was made, but before the  September 29 trunk
> build was made.

Wow.. yes. As a matter of fact, all the issues including the one connected with this bug report here seem to have been introduced on the Sept. 29 trunk build. Sorry for my mixup.
I see this too on recent trunk - and I can also confirm the regression range (between 2006-09-28-06 and 2006-09-29-06). It's like it's enough to open the context menu - once it's opened, the link will open in a new window. Firefox seems to have related/similar issue if you Ctrl+click (right-click) a link (bookmark) in the personal toolbar - when the context menu appears the link will open in the same window. However, in Firefox, I don't see the  issue when Ctrl-clicking links in webpages...
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
I'm not 100% this (link open behaviour) is cocoa-related so I'm dropping it in XP Apps ftm.
Assignee: general → jag
Component: General → XP Apps
QA Contact: general
OK, right-click works - but ctrl-click doesn't
(In reply to comment #7)
> OK, right-click works - but ctrl-click doesn't
> 

I am unable check right-clicks. 
I only have the standard single-button mouse on my Macs, so I always have to use CTRL+Click.
Flags: blocking-seamonkey1.5?
Blocks: cocoa
Keywords: regression
Fixed by the patch in bug 361240

*** This bug has been marked as a duplicate of 361240 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Well, fixed by the patch that wasn't checked in, which isn't quite as helpful.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Depends on: 362812
This is now fixed by the the patch in bug 362812.
Status: REOPENED → RESOLVED
Closed: 18 years ago18 years ago
Resolution: --- → FIXED
Flags: blocking-seamonkey2.0a1?
You need to log in before you can comment on or make changes to this bug.