On Wed, 7 Mar 2012, Christian Schmidt wrote:
Assume you have a form of some kind. If the server-side validation
fails, you want to load the same page again (this time with an error
message) in the same window, but if the server-side validation succeeds,
you want to open a new window, e.g.
Bjartur Thorlacius skrev 2012-03-09 10:43:
I argue that putting user interface hints into a file transfer
protocol does cause problems
Would it be better if the Window-Target was somehow specified in the
head of the destination page, or is that just another way of doing the
same?
In
On Wed, 14 Mar 2012 19:59:50 -, Christian Schmidt whatwg@chsc.dk
wrote:
Bjartur Thorlacius skrev 2012-03-09 10:43:
I argue that putting user interface hints into a file transfer
protocol does cause problems
Would it be better if the Window-Target was somehow specified in the
head of
On 3/14/12 3:59 PM, Christian Schmidt wrote:
Bjartur Thorlacius skrev 2012-03-09 10:43:
I argue that putting user interface hints into a file transfer
protocol does cause problems
Would it be better if the Window-Target was somehow specified in the
head of the destination page
That's pretty
On 3/8/12, Christian Schmidt whatwg@chsc.dk wrote:
AFAIK no modern browser implements Window-Target, so I don't think the
we need to reuse the old header name. Expanding Content-Disposition is
also an option, e.g. Content-Disposition: inline; target=_blank.
Unfortunately we cannot use
On 2012-03-08 20:25, Christian Schmidt wrote:
...
Separating the network protocol from the user interface seems highly
desirable. Window-Target sacrifices that.
I get your point. But it seems that Content-Disposition already suffers
from this.
RFC 2183 describes the Content-Disposition like
Thanks for commenting on my suggestion.
Bjartur Thorlacius wrote on 2012-03-07 23:53:
We should describe the security implications of lifting said
restrictions (if any) in the rationale document, for when someone is
burdened by these restrictions and can't figure if they were added
for erring
On a and form elements you can specify a target attribute, e.g.
_blank. But sometimes you don't know whether to open in _self or _blank
at the time the link is clicked/the form is submitted.
I suggest that a server can specify a link target in an HTTP header,
e.g. Window-Target: _blank. The
On Wed, 07 Mar 2012 22:19:17 -, Christian Schmidt whatwg@chsc.dk
wrote:
I suggest that a server can specify a link target in an HTTP header,
e.g. Window-Target: _blank. The page would be equivalent to specifying
the same value in the form or a tag leading to the page. It should
