WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
11855
Opening a new window for a link rather than a tab
https://bugs.webkit.org/show_bug.cgi?id=11855
Summary
Opening a new window for a link rather than a tab
Patricia Warwick
Reported
2006-12-16 15:14:58 PST
I'm not sure if this is a bug but the behaviour differs from that of Firefox. I have specified in the preferences that I want to open links from application in a new tab in the current window ... but when I click on a link in an email (Apple Discussions:
http://discussions.apple.com/thread.jspa?messageID=3715540#3715540
), in Firefox this gets opened as new tab in the current window but in Webkit it opens in a new window ... Here is the raw source from a similar eMail" Delivered-To:
patricia.warwick@gmail.com
Received: by 10.70.13.11 with SMTP id 11cs774576wxm; Fri, 15 Dec 2006 17:14:42 -0800 (PST) Received: by 10.35.119.11 with SMTP id w11mr2607370pym.1166231682518; Fri, 15 Dec 2006 17:14:42 -0800 (PST) Return-Path: <
discusswatch@apple.com
> Received: from c1-outbound1.webmaillogin.com (c1-outbound1.webmaillogin.com [216.40.35.249]) by mx.google.com with ESMTP id f57si4731995pyh.2006.12.15.17.14.42; Fri, 15 Dec 2006 17:14:42 -0800 (PST) Received-SPF: softfail (google.com: domain of transitioning
discusswatch@apple.com
does not designate 216.40.35.249 as permitted sender) Received: from egress4.webmaillogin.com ([216.40.36.156]) by c1-outbound1.webmaillogin.com with esmtp (Exim 3.36 #1 (Debian)) id 1GvO8Q-0007IF-00 for <
patricia.warwick@gmail.com
>; Fri, 15 Dec 2006 20:14:42 -0500 Received: by egress4.webmaillogin.com (egress4.webmaillogin.com, from userid 1005) id 32C11770390; Fri, 15 Dec 2006 20:14:41 -0500 (EST) Received: from webmaillogin.com (fr5.webmaillogin.com [216.40.35.69]) by egress4.webmaillogin.com (egress4.webmaillogin.com) with ESMTP id 04B1D77005B for <
patricia.warwick@gmail.com
>; Fri, 15 Dec 2006 20:14:39 -0500 (EST) X-Trusted: false Received: from c1m27.emaildefenseservice.com ([216.40.36.60] verified) by fr5.webmaillogin.com (CommuniGate Pro SMTP 5.0.9) with SMTP id 284776977 for
patricia@patriciawarwick.com
; Fri, 15 Dec 2006 20:14:39 -0500 Received: from bz1.apple.com [17.254.13.36] (EHLO bz1.apple.com) by c1m27.emaildefenseservice.com (mxl_mta-1.3.8-10p10) with ESMTP id d7843854.28395.020.c1m27; Fri, 15 Dec 2006 20:14:37 -0500 (EST) Received: from acutil02.apple.com ([17.112.146.78]) by bz1.apple.com (8.13.8/8.13.8) with ESMTP id kBG1Eb2S022932 for <
patricia@patriciawarwick.com
>; Fri, 15 Dec 2006 17:14:37 -0800 (PST) Message-ID: <
6218340.1166231513835.JavaMail.root@acutil02.apple.com
> Date: Fri, 15 Dec 2006 17:11:53 -0800 From: Apple Discussions Subscriptions <
discusswatch@apple.com
> To: Patricia Warwick <
patricia@patriciawarwick.com
> Subject: Topic "Launching different iDVD project while processing another causes crash" in the Apple Discussions forum "iDVD 6" has been updated by SDMacuser Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_53731_12819576.1166231513731" Content-Disposition: inline X-Spam: exempt X-MAIL-FROM: <
discusswatch@apple.com
> X-SOURCE-IP: [17.254.13.36] ------=_Part_53731_12819576.1166231513731 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Dear Patricia Warwick, You have requested mail to be sent to you when messages to the Apple Discussions topic "Launching different iDVD project while processing another causes crash" are posted. SDMacuser posted "Launching different iDVD project while processing another causes crash" on Dec 15, 2006 5:11:53 PM. To view the topic, visit:
http://discussions.apple.com/thread.jspa?messageID=3711328#3711328
To view the forum, visit:
http://discussions.apple.com/forum.jspa?forumID=1121
. ======================================================================== IF YOU ARE THE AUTHOR OF THE ORIGINAL QUESTION: ======================================================================== When you return to view the answers, please mark responses appropriately. Simply login and select the value you desire for applicable responses. As the author of the original question, you may assign a helpfulness value to responses. Please use the following when rating a response: None: The response was simply a point of clarification to my original question or didn't really help. Helpful: This response helped with a portion of my question, but I still need some additional help. Solved: This response has solved my problem completely. WHY SHOULD I DO THIS? In short, here are 3 reasons why it's worth a few moments of your time: 1) Other members have taken time out of their day to assist you, so please take a moment to give them credit for the assistance they have provided. 2) Your rating not only helps your peers earn points toward their status in Discussions, but validates the quality of the solution you've received. 3) Other readers will be able determine which response(s) helped solve the original question, which will greatly enhance the knowledge and experience for all community members and visitors. ======================================================================== We appreciate your participation in Apple Discussions. Thank you for being part of our community. Apple Discussions Team --- Please note that you have requested to receive these notifications by subscribing to a topic on Apple Discussions. If you would like to stop receiving notifications: 1) Visit
http://discussions.apple.com
2) Login, if you have not already 3) Click the "My Subscriptions" on the right hand side of your browser window. 4) In the Subscribed Topics area, select the delete option. mail-id: 128:1121:766016:3711328:328521:Patricia W ------=_Part_53731_12819576.1166231513731--
Attachments
Add attachment
proposed patch, testcase, etc.
David Kilzer (:ddkilzer)
Comment 1
2006-12-17 08:24:27 PST
This is most likely a Safari browser issue, not a WebKit issue, and thus would require a Radar file filed through
https://bugreport.apple.com/
. If you file a bug there, please report the bug number here, and add the "InRadar" keyword. You may sign up for a free "Online" ADC membership using
https://connect.apple.com/
.
Patricia Warwick
Comment 2
2006-12-17 09:56:21 PST
Please let me know how I can determine whether a problem is in Safari vs. Webkit? Originally I reported a problem incorrectly against Webkit because I had forgotten to change my default browser to Webkit. But now it is and I should only be using Webkit from now on. This opening a new window is happening when I am using Webkit (as well as Safari.) Is there some way of identifying the component that is not working correctly?
David Kilzer (:ddkilzer)
Comment 3
2006-12-17 11:25:50 PST
(In reply to
comment #2
)
> Please let me know how I can determine whether a problem is in Safari vs. > Webkit? Originally I reported a problem incorrectly against Webkit because I > had forgotten to change my default browser to Webkit. But now it is and I > should only be using Webkit from now on. This opening a new window is happening > when I am using Webkit (as well as Safari.) Is there some way of identifying > the component that is not working correctly?
What I mean is that the decision to open a new window versus open a new tab *may* be in the Safari application itself rather than in the WebKit framework. If it's a part of Safari, this behavior can't be changed by patching WebKit, it must be changed by patching Safari, only Apple can do that. I don't know enough about WebKit to know where this decision is, so someone with more information needs to answer this question. What would be helpful in the meantime, though, is to know whether this behavior is the same with Safari and with the WebKit nightly. Please test the behavior and report back here.
Patricia Warwick
Comment 4
2006-12-17 13:01:41 PST
It definitely happens in WebKit as well as in Safari. When my cursor is positioned over the link it states it will open the link in a new window which it does. But as I noted, Firefox does not.
Patricia Warwick
Comment 5
2006-12-19 07:13:08 PST
I've opened this as a new Safari bug # 4891111
David Kilzer (:ddkilzer)
Comment 6
2006-12-19 07:48:12 PST
(In reply to
comment #5
)
> I've opened this as a new Safari bug # 4891111
<
rdar://problem/4891111
>
Robert Blaut
Comment 7
2008-02-19 03:07:14 PST
It isn't Webkit issue.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug