- From: Anne van Kesteren <annevk@opera.com>
- Date: Sat, 27 Sep 2008 11:27:10 +0200
- To: "Ian Hickson" <ian@hixie.ch>, "Boris Zbarsky" <bzbarsky@mit.edu>
- Cc: "HTML WG" <public-html@w3.org>
On Sat, 27 Sep 2008 02:11:02 +0200, Ian Hickson <ian@hixie.ch> wrote: > On Fri, 26 Sep 2008, Boris Zbarsky wrote: >> If nothing else (for things like Access-Control) to differentiate a UA >> that doesn't support the spec at all from a UA that happens to be doing >> things with a unique identifier origin... > > Wouldn't the "null" value that has to be passed in such cases be enough > to detect those cases? Actually, per a recent update it will be the empty string. (It references the ASCII origin string from HTML5.) This still allows you to differentiate between legacy and modern clients though, as legacy clients won't include the header. On Sat, 27 Sep 2008 03:01:35 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote: > Ian Hickson wrote: >> My understanding is that the specs now have just two functions (one for >> ASCII and one for Unicode). Is this not the case? > > No, because various places in the spec rely on different behaviors for > the non-triple origins. Why do you need a string serialization for those cases? I don't think you do. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Saturday, 27 September 2008 09:28:08 UTC