Re: [XHR] send doesn’t explain what to do when method is GET

Jonas Sicking wrote:
> But not saying anything is likely to hurt compatibility between 
> implementations and make authors rely on features that only work in some 
> browsers.

But saying something is going to profile HTTP. This may or may not be a 
useful extension point, and it shouldn't be closed down by this WG. 
Please leave HTTP questions to the HTTP working group.

What's next? Disallowing non-RFC2616 methods because Opera screws them 
up? Why not fix the implementations instead?

BR, Julian