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

[whatwg] Proposal: target="_tab"

From: Joćo Eiras <joao.eiras@gmail.com>
Date: Thu, 12 Jun 2008 18:17:19 +0100
Message-ID: <e72b1b360806121017t13d282afwdd8860cc4a022071@mail.gmail.com>
Hi ! I didn't saw that reply.

> I'm not sure why you keep insisting that it's up to the browser -- IMO, it's
> up to the USER.

You're not understanding me:
when I say browser, obviously I mean client, client-side, browser,
user or whatever you want to call it, as opposed to web application or
server-side

> Also, having means to open new tabs as opposed to new windows in the specs
> is nothing against the user preference, in fact, it helps to express the
> user preference if the browser fails to provide it.

Then we're going to bloat a specification due to browser idiosyncrasies ?
Allowing a page to control such behavior would be bad. Currently
browsers with tabbed interface manage to unclutter the taskbar and
desktop, while aggregate pages inside a single window, which is
overall good for the user's experience, good for performance, good
usability.

We'd be providing a mechanism that is not backwards compatible with
the current state of the art user agents, although we've seen that new
features heavily demanded get implemented quickly, and we'd be
providing, again, authors with mechanism to degrade the user's
experience.

I can't honestly come up with a single reason why a webpage should
open a new window instead of tab. All use cases you can come up fit
better if new tabs are open. If you don't like the fact that a tab
fits the entire window, you can either detach it, your use a user
agent that support MDI interface.

With all this say now your going to tell me I'm contradicting myself
by supporting windows now. No, you'd be wrong. I'd expect a browser to
always open tabs if there's a _blank target. Having _target and_tab
would require UA's to support two different way of opening new pages:
tabbed and detached ones.

For me it's all a matter of letting the user control the web page.

Considering this discussion is still going to last a bit, and
everything significant that could be said by me and others was said, I
rest my case.

Cheers.


2008/6/12 Kristof Zelechovski <giecrilj at stegny.2a.pl>:
> Programmatically controlling the containment of a new window is a two-edged
> sword: you can provide for the lame user agent but you can also override
> user settings.  The latter possibility is more painful; upgrading the
> browser is easier than dealing with an impertinent Web site.
> IMHO,
> Chris
> P.S.: If you want your answer to go to Jo?o only, just send it exclusively
> to him.
>
> -----Original Message-----
> From: Borek Bernard [mailto:borekbe at yahoo.co.uk]
> Sent: Thursday, June 12, 2008 11:25 AM
> To: Joao Eiras; Kristof Zelechovski; Ian Hickson; whatwg at lists.whatwg.org
> Subject: Re: [whatwg] Proposal: target="_tab"
>
> Hi Jo?o,
>
> I'm not sure why you keep insisting that it's up to the browser -- IMO, it's
> up to the USER. Please read all my arguments before, it's not true that a
> user using a tabbed browser always prefers opening new tabs instead of new
> windows. That's just your user preference.
>
> Also, having means to open new tabs as opposed to new windows in the specs
> is nothing against the user preference, in fact, it helps to express the
> user preference if the browser fails to provide it.
>
>
>
>
Received on Thursday, 12 June 2008 10:17:19 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:03 UTC