On Wed, 06 Mar 2013 18:55:27 +0100, Ian Hickson wrote:
On Wed, 6 Mar 2013, Simon Pieters wrote:
On Mon, 14 Jan 2013 09:40:56 +0100, Henri Sivonen
wrote:
> Would it be terrible to make attempts to mutate the 'is' attribute
> throw thereby teaching authors who actually try to mutate it that
On Wed, 6 Mar 2013, Simon Pieters wrote:
> On Mon, 14 Jan 2013 09:40:56 +0100, Henri Sivonen wrote:
>
> > Would it be terrible to make attempts to mutate the 'is' attribute
> > throw thereby teaching authors who actually try to mutate it that it's
> > not mutable?
>
> We already have several a
On Mon, 14 Jan 2013 09:40:56 +0100, Henri Sivonen wrote:
Would it be terrible to make attempts to mutate the 'is' attribute
throw thereby teaching authors who actually try to mutate it that it's
not mutable?
We already have several attributes that are immutable but don't throw or
anything w
Whilst on the topic of base64, has anyone considered adding support for
base64url ?
…Mark
On Mar 4, 2013, at 10:29 AM, Kenneth Russell wrote:
> On Mon, Mar 4, 2013 at 10:04 AM, Joshua Bell wrote:
>> On Mon, Mar 4, 2013 at 9:09 AM, Boris Zbarsky wrote:
>>
>>> The problem I'm trying to solve i
On Wed, Mar 6, 2013 at 2:46 PM, Anne van Kesteren wrote:
> So HTML's "potentially CORS-enabled fetch" is incompatible with
> XMLHttpRequest.
Turns out the wonderful browsers are not implementing XMLHttpRequest!
So XMLHttpRequest could do the same as HTML's "potentially
CORS-enabled fetch" I thin
It seems we have a bunch of different policies for setting the Origin header :-(
XMLHttpRequest always sets it to the given value.
HTML's "fetch" only sets it to a non-null value if a from parameter is passed.
HTML's "potentially CORS-enabled fetch" seems to never invoke "fetch"
with a from para
