[whatwg] Specify href target with HTTP headers

Wed Mar 14 12:59:50 PDT 2012

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 special, having two identifiers for the same resource, one for
> when the resource is to be navigated to in an existing browsing
> context and another for when navigation to the resource implies
> creation of a new browsing context, breaks identification.
It was not my suggestion to use to introduce more URLs. But a resource 
that is designed to be used in an iframe context often does not make 
sense to load in the entire browser window (pages loaded in an iframe 
often do not contain navigation, header, footer etc.), so in practice I 
think a resource is often somewhat “tailored” to a specific browsing 
context.


> I don't know if my pie in the sky thought should be taken seriously,
>  but why would I want another copy of the form I just submitted? I
> just want the error messages.
I'm not sure I understand what you mean. The usual way of doing
server-side validation of a form (e.g. a login form) is to submit it and
- in case the validation fails - to show the same form prefilled with
the same data but with red boxes around the invalid fields, error
messages, help texts, etc. Of course you can do this by submitting the
form via AJAX and then manipulate the DOM via JavaScript, but that is
complex.

-- 
Christian Schmidt