ding my points. But your
view is quite common as I've learned :)
Regards,
Borek
- Original Message
From: João Eiras <[EMAIL PROTECTED]>
To: Borek Bernard <[EMAIL PROTECTED]>; whatwg@lists.whatwg.org
Sent: Thursday, 12 June, 2008 7:17:19 PM
Subject: Re: [whatwg] Pr
ill probably have hard times understanding my points. But your
> view is quite common as I've learned :)
> Regards,
> Borek
>
>
>
> - Original Message ----
> From: João Eiras <[EMAIL PROTECTED]>
> To: Borek Bernard <[EMAIL PROTECTED]>; whatwg@lists.wha
But your view is quite common as I've learned :)
Regards,
Borek
- Original Message
From: João Eiras <[EMAIL PROTECTED]>
To: Borek Bernard <[EMAIL PROTECTED]>; whatwg@lists.whatwg.org
Sent: Thursday, 12 June, 2008 7:17:19 PM
Subject: Re: [whatwg] Proposal: target=&quo
sier 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:[EMAIL PROTECTED]
> Sent: Thursday, June 12, 2008 11:25 AM
>
.: If you want your answer to go to João only, just send it exclusively
to him.
-Original Message-
From: Borek Bernard [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 12, 2008 11:25 AM
To: Joao Eiras; Kristof Zelechovski; Ian Hickson; whatwg@lists.whatwg.org
Subject: Re: [whatwg] Proposal
: Wednesday, 11 June, 2008 9:15:47 PM
Subject: Re: [whatwg] Proposal: target="_tab"
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 web
11, 2008 9:16 PM
To: Kristof Zelechovski; 'Borek Bernard'; 'Ian Hickson';
whatwg@lists.whatwg.org
Subject: Re: [whatwg] Proposal: target="_tab"
As mentioned multiple times, that up to the user agent, or browser if you
prefer, to control. Users with browsers with ta
Borek Bernard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 11:27 AM
To: Kristof Zelechovski; Ian Hickson; whatwg@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
Hickson; whatwg@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 a
On Wed, 11 Jun 2008, Jens Meiert wrote:
> > >
> > > What is interesting though is that authors can let open new
> > > windows/tabs by HTML, CSS, /and/ scripting. I am not sure if this
> > > functionality, that may ultimately impede user experience, can
> > > really be considered structural, pres
> > What is interesting though is that authors can let open new windows/tabs
> > by HTML, CSS, /and/ scripting. I am not sure if this functionality, that
> > may ultimately impede user experience, can really be considered
> > structural, presentational, /and/ behavioral.
>
> I have no idea what you
On Wed, 11 Jun 2008, Jens Meiert wrote:
> > >
> > > In http://forums.whatwg.org/viewtopic.php?t=185 it is proposed that
> > > authors should have the ability to suggest that links open in new
> > > windows and new tabs. The suggested solution is to introduce a new
> > > browsing context keyword
Wednesday, 11 June, 2008 10:42:41 AM
Subject: Re: [whatwg] Proposal: target="_tab"
Once you have support in CSS, you can use DOM+CSS from JS. No particular
support within JS is required.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Borek B
> > In http://forums.whatwg.org/viewtopic.php?t=185 it is proposed that
> > authors should have the ability to suggest that links open in new
> > windows and new tabs. The suggested solution is to introduce a new
> > browsing context keyword "_tab".
>
> In general, it's best to let users decide whe
Subject: Re: [whatwg] Proposal: target="_tab"
Hi Ian,
What do you think about the GReader use case? In my eyes, it makes the _tab
scenario quite valid.
But, as mentioned by Adrian Sutton, there would be technical problems with
older browsers so this proposal has to be scrapped. On th
Hi Ian,
What do you think about the GReader use case? In my eyes, it makes the _tab
scenario quite valid.
But, as mentioned by Adrian Sutton, there would be technical problems with
older browsers so this proposal has to be scrapped. On the HTML/CSS level, this
will be eventually handled by the
.whatwg.org
Sent: Tuesday, 10 June, 2008 10:29:54 PM
Subject: Re: [whatwg] Proposal: target="_tab"
>> From my brief testing, _tab opens a new window so it should be backwards
>> compatible.
It's deceptively close but not quite backwards compatible. _tab will cause
the link t
On Tue, 10 Jun 2008, Simon Pieters wrote:
>
> In http://forums.whatwg.org/viewtopic.php?t=185 it is proposed that
> authors should have the ability to suggest that links open in new
> windows and new tabs. The suggested solution is to introduce a new
> browsing context keyword "_tab".
>
> Use c
>> From my brief testing, _tab opens a new window so it should be backwards
>> compatible.
It's deceptively close but not quite backwards compatible. _tab will cause
the link to open in the frame called "_tab" and if it doesn't exist it
creates it, as a new window. So the first link works perfectl
>From my brief testing, _tab opens a new window so it should be backwards
>compatible.
- Original Message
From: João Eiras <[EMAIL PROTECTED]>
To: Borek Bernard <[EMAIL PROTECTED]>; whatwg@lists.whatwg.org
Sent: Tuesday, 10 June, 2008 6:03:51 PM
Subject: Re: [whatwg
This approach however has two problems:
- user agent that don't support _tab which would have to interpret as
_blank, or _self, so this case need to be predicted in the spec, if any
- that value is not backwards compatible. I'd expect for an user agent
that does not support tabs to open a ne
> I don't believe it should be up to the document author to distinguish
> between a page opened up in a new window or new tab, since that is
> entirely a browser interface issue. Since several browsers already treat
> _blank in that way anyway, introducing a new keyword doesn't s
IMO, both _blank and _tab should always open in the same window, under a
new tab. ... Browsers currently already support this. So, I think it's
therefore redundant.
As you stated, that is your user preference and my preference can be different.
You are lucky that your preference
Wondering: How is CSS 3's Hyperlink Presentation Module [1] (and its
"target-new" property) supposed to fit in, /theoretically/ allowing us to
drop @target altogether?
That looks great (didn't know of that!), that would sort out the HTML/CSS part
of game (although implementing ta
Simon Pieters wrote:
In http://forums.whatwg.org/viewtopic.php?t=185 it is proposed that
authors should have the ability to suggest that links open in new
windows and new tabs. The suggested solution is to introduce a new
browsing context keyword "_tab".
I don't believe it should be up to the
IMO, both _blank and _tab should always open in the same window, under a
new tab. Else that would be bad usability.
Browsers currently already support this.
So, I think it's therefore redundant.
Na , Simon Pieters <[EMAIL PROTECTED]> escreveu:
In http://forums.whatwg.org/viewtopic.php?t=185 it
> In http://forums.whatwg.org/viewtopic.php?t=185 it is proposed that authors
> should have the ability to suggest that links open in new windows and new
> tabs. The suggested solution is to introduce a new browsing context keyword
> "_tab".
Wondering: How is CSS 3's Hyperlink Presentation Module
In http://forums.whatwg.org/viewtopic.php?t=185 it is proposed that
authors should have the ability to suggest that links open in new windows
and new tabs. The suggested solution is to introduce a new browsing
context keyword "_tab".
Use case for opening a new window with specified size: he
28 matches
Mail list logo
