W3C slaps down Google's proposal to treat multiple domains as same origin
1–10 of 128 posts
Re: W3C slaps down Google's proposal to treat multiple domains as same origin
#2What a weird coincidence that this would really help let's say a company that used google.com as well as google.co.uk and doubleclick.com as their "first party" set. Good that W3C stopped it.
Re: W3C slaps down Google's proposal to treat multiple domains as same origin
#3What a weird coincidence that this would really help let's say a company that used google.com as well as google.co.uk and doubleclick.com as their "first party" set. Good that W3C stopped it.
W3C doesn't really have any real power over what happens in the internet today. It's browser vendors associated with WHATWG that draw the straws now.
Re: W3C slaps down Google's proposal to treat multiple domains as same origin
#4Hmmm, what stops Google from doing it anyway? Chrome is the de-facto standard nowadays with every other browser being under 10% market share except Safari holding out around 20%.
Re: W3C slaps down Google's proposal to treat multiple domains as same origin
#5How did w3c get such power to “slap down” google.
If users can’t access gmail / YouTube etc, they will be ignoring the w3c.
Another workaround if google can’t try this in chrome (it can) do cookies on a google sub domain (yt.google.com etc)
Re: W3C slaps down Google's proposal to treat multiple domains as same origin
#6Hmmm, what stops Google from doing it anyway? Chrome is the de-facto standard nowadays with every other browser being under 10% market share except Safari holding out around 20%.
Depends what sites you look at - for many consumer sites in the UK Chrome / Safari split on mobile is close to equal and 60%+ of visitors are on mobile
Chrome not being available on iOS is good from an anti-monoculture perspective but not so good from a browser feature perspective
Re: W3C slaps down Google's proposal to treat multiple domains as same origin
#7What a weird coincidence that this would really help let's say a company that used google.com as well as google.co.uk and doubleclick.com as their "first party" set. Good that W3C stopped it.
W3C doesn't really have any real power over what happens in the internet today. It's browser vendors associated with WHATWG that draw the straws now.
Correction: it's the single browser vendor that draws the straws now. And it's Google. They've literally stopped caring about any objections to any of their proposals and just ship them.
Re: W3C slaps down Google's proposal to treat multiple domains as same origin
#8How did w3c get such power to “slap down” google. If users can’t access gmail / YouTube etc, they will be ignoring the w3c. Another workaround if google can’t try this in chrome (it can) do cookies on a google sub domain (yt.google.com etc)
> If users can’t access gmail / YouTube etc, they will be ignoring the w3c.
Are users unable to access gmail / YouTube etc now?
Re: W3C slaps down Google's proposal to treat multiple domains as same origin
#9What a weird coincidence that this would really help let's say a company that used google.com as well as google.co.uk and doubleclick.com as their "first party" set. Good that W3C stopped it.
W3C doesn't really have any real power over what happens in the internet today. It's browser vendors associated with WHATWG that draw the straws now.
Given Chrome's market share, that is mostly Google.
The irony that IE fighters are the same that helped Google reached their position, because "developer tools" and "don't like FF UI changes".
Now don't complain, how is it again? Ah, Chrome is available as open source so it isn't comparable to IE.
Re: W3C slaps down Google's proposal to treat multiple domains as same origin
#10Earlier quoted context omitted.
W3C doesn't really have any real power over what happens in the internet today. It's browser vendors associated with WHATWG that draw the straws now.
Correction: it's the single browser vendor that draws the straws now. And it's Google. They've literally stopped caring about any objections to any of their proposals and just ship them.
Just look at Project Fugu. Google is putting the implementation first, the spec to "standards wash" their implementation comes later. And if WHAT WG doesn't want to play along (and why wouldn't they? most browser vendors are now downstream from Chromium so they get the implementation by default) they can just leave it in as "experimental" with a "draft" spec. W3C doesn't really get a say in this.