Re: Key Events internationalization

2007-08-29 Thread Bjoern Hoehrmann
* Richard Ishida wrote: >The DOM appendix A gives an example of pressing the key engraved with Q >on a US physical kbd with a serbian mapping applied. The example quotes >the result as "keydown": "U+0409". How is the implementation supposed >to figure out that the appropriate identifier is U+040

Key Events internationalization

2007-08-29 Thread Richard Ishida
[Forwarding to the webapi folks an edited version of an earlier message to i18n] http://www.w3.org/TR/DOM-Level-3-Events/keyset.html One thing I currently don't have a clear grasp of is the following: The DOM appendix A gives an example of pressing the key engraved with Q on a US physical kbd

Re: XHR: definition of same-origin

2007-08-29 Thread Boris Zbarsky
Bjoern Hoehrmann wrote: The URLs are equivalent, if you send different Host headers, that's your choice, but it's neither required nor otherwise necessary. As an example Internet Explorer 6 will not send the default port in the Host header For what it's worth, neither will Gecko. It will also

Re: XHR: definition of same-origin

2007-08-29 Thread Maciej Stachowiak
On Aug 29, 2007, at 12:52 AM, Bjoern Hoehrmann wrote: * Maciej Stachowiak wrote: The requests will be sent with different 'Host' http request headers headers. A server configured as a virtual host could easily return different content for "example.com:443" and "example.com". So it's not imm

Re: XHR: definition of same-origin

2007-08-29 Thread Bjoern Hoehrmann
* Maciej Stachowiak wrote: >The requests will be sent with different 'Host' http request headers >headers. A server configured as a virtual host could easily return >different content for "example.com:443" and "example.com". So it's not >immediately obvious that they are the same resource id

Re: XHR: definition of same-origin

2007-08-29 Thread Maciej Stachowiak
On Aug 29, 2007, at 12:03 AM, Boris Zbarsky wrote: Maciej Stachowiak wrote: Any definition of a same-origin policy would have to define how to determine the hostname and port. For what it's worth, an origin in Gecko also includes the scheme. This handles things like http-to-https access

Re: XHR: definition of same-origin

2007-08-29 Thread Boris Zbarsky
Maciej Stachowiak wrote: Any definition of a same-origin policy would have to define how to determine the hostname and port. For what it's worth, an origin in Gecko also includes the scheme. This handles things like http-to-https access (not allowed), unknown schemes (only same-origin with