WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WONTFIX
14961
extend frame target types to support _tab
https://bugs.webkit.org/show_bug.cgi?id=14961
Summary
extend frame target types to support _tab
James Cox
Reported
2007-08-13 19:52:37 PDT
opening a link which targets _new causes the current window to lose focus. This is undesirable behavior as often the user may just be opening the link to preload the content for review later. It'd be nice therefore for responsible web developers to target _tab, which would default to _new when tabs are disabled. given most browsers now support tabs, this makes sense to work into any HTML/XHTML specs due to be released, but till then, and given the prevalence of web2.0 apps and so on making real use of _new, support for _tab would be desirable. a further option for browsers who support this could be a preference which forces all _new links to open in tabs.
Attachments
Add attachment
proposed patch, testcase, etc.
David Kilzer (:ddkilzer)
Comment 1
2007-08-13 23:21:32 PDT
Does HTML5 mention this?
Ian 'Hixie' Hickson
Comment 2
2007-08-13 23:30:12 PDT
The "_new" value is actually "_blank", not "_new". The HTML5 spec doesn't define "_tab", in fact it actually makes the existing value "_blank" non-conforming. Authors shouldn't use it. However, it is expected that tabbed browsers would take the existing "_blank" value and use that to target new tabs. I recommend against supporting "_tab".
Adam Barth
Comment 3
2010-09-20 02:09:16 PDT
Ok. No _tab then.
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