W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2008

[whatwg] Proposal: target="_tab"

From: Joćo Eiras <joao.eiras@gmail.com>
Date: Wed, 11 Jun 2008 20:15:47 +0100
Message-ID: <op.uclmghx0jz3wb9@mors.wag54gs>
As mentioned multiple times, that up to the user agent, or browser if you  
prefer, to control. Users with browsers with tabbed interface want tabs  
and that it. Leaving such usability in control of a webpage is bad. All  
browser that support tabs allow the user to choose if they want the  
browser to open new windows of just tabs.

Na , Kristof Zelechovski <giecrilj at stegny.2a.pl> escreveu:

> You can use A.click instead of window.open.  I have ignored the keyboard
> shortcut requirement because it is irrelevant.
> I agree that modifying window.open to support tabs would be more  
> consistent;
> I just wanted to make you realize that neither is it strictly necessary  
> nor
> does it require any support from JS itself (your postulated modification  
> of
> the window.open interface method is perfectly suited for the current JS
> language, I hope?).
> HTH,
> Chris
>
> -----Original Message-----
> From: Borek Bernard [mailto:borekbe at yahoo.co.uk]
> Sent: Wednesday, June 11, 2008 11:27 AM
> To: Kristof Zelechovski; Ian Hickson; whatwg at lists.whatwg.org
> Subject: Re: [whatwg] Proposal: target="_tab"
>
> Hi Kristof,
>
> my knowledge of JS is limited but how would you handle this situation:
> in your web app, you want to provide a keyboard shortcut for opening
> current item into a new tab. You need to invoke this action from  
> JavaScript
> so setting CSS to some DOM element is not enough (AFAIK). I think
> window.open() would need some new optional parameter or something  
> similar to
> support this.
>
> ---
> Borek
>
>
>
Received on Wednesday, 11 June 2008 12:15:47 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:41 UTC