5 ms·
Is this a mistake or Google trying to force the standards process in their favour? Users seem to be blaming Firefox, not Google.
by skrebbel 12y ago
Is this a mistake or Google trying to force the standards process in their favour? Users seem to be blaming Firefox, not Google.
- bagder 12y agoThis doesn't drive the standards process in any particular direction, this is just a broken implementation that doesn't adhere to the current standard draft!
- skrebbel 12y agoIt could drive the standards process in a particular direction if it would compel Firefox to implement Google's HTTP2 vision, so that beta users can log into Google services again. Then, suddenly, two major browser vendors support a particular blend of HTTP2, significantly increasing the chance of that road being taken. It sounds overly mischievous though (and I doubt Mozilla will bend), so my bet is that it's a mistake.
- hmsimha 12y agoI'm reminded of this passage from Mark Pilgrim's Dive into HTML5 > But none of this answers the original question: why do we have an <img> element? Why not an <icon> element? Or an <include> element? Why not a hyperlink with an include attribute, or some combination of rel values? Why an <img> element? Quite simply, because Marc Andreessen shipped one, and shipping code wins. > That’s not to say that all shipping code wins; after all, Andrew and Intermedia and HyTime shipped code too. Code is necessary but not sufficient for success. And I certainly don’t mean to say that shipping code before a standard will produce the best solution. Marc’s <img> element didn’t mandate a common graphics format; it didn’t define how text flowed around it; it didn’t support text alternatives or fallback content for older browsers. And 17 years later, we’re still struggling with content sniffing, and it’s still a source of crazy security vulnerabilities. And you can trace that all the way back, 17 years, through the Great Browser Wars, all the way back to February 25, 1993, when Marc Andreessen offhandedly remarked, “MIME, someday, maybe,” and then shipped his code anyway. > The ones that win are the ones that ship. I'm not convinced it's a mistake, and it wouldn't be the first time a browser maker tried to influence the direction of web.
- kalleboo 12y agoIt sounds like it doesn't work in Chrome either, so it's just broken.
- higherpurpose 12y agoWas it typical behavior of SPDY before to block the connection unless it could pass cookies through? If not, then it definitely feels like Google is trying to force cookie-usage through the protocol, and by shipping it like this, it forces browser vendors to adopt it as-is.
- spindritf 12y agoHow do you imagine logging in without a cookie? And the browser in question supports cookies, it's just a bug. This whole thread is just full of some weird anti-Google paranoia way beyond any healthy level of scepticism.
- perlgeek 12y agoIt is a mistake that Google rolls out a new protocol implementation without testing it in the two known major products that support it.
- josteink 12y ago> Is this a mistake or Google trying to force the standards process in their favour? Users seem to be blaming Firefox, not Google. Given Google's history around this whole HTTP/2.0 shenanigans, I see little reason to see anything in their favour. They are probably gambling that Firefox will fold (like they forced them to with DRM) so that once again, they can have it their way internet-wide without having to wait for annoying things like feedback from others and standards-committees and such. They will probably win.
- dmm 12y agoGoogle directly funds the Mozilla foundation with about 300 million USD per year. If Google wanted to see firefox fall they have a very direct way of achieving it.
- annnnd 12y agoNot true - they don't pay this money out of charity. I am guessing other companies with interest in having a leading search engine (MS and Yahoo primarily, but also Apple, Amazon,...) would probably be happy to take Google's place if they backed out (maybe not for the same amount though).
- cookiecaper 12y agoThis could be seen as a technique to undermine Firefox and get more users to Chrome, which would devalue Firefox's contribution to Google. As Google appears to embrace standards but continues to implement little flaws and Chrome-only behaviors (that is, extend), they will eventually deplete Firefox's market share to the point where such a monetary transfer is no longer beneficial (extinguish). People always bring up the fact that there is some value currently provided by Google's payment to Firefox like there's no problem with the vast majority of the Mozilla Foundation's funding coming from a competing entity. It's still a dangerous situation, even if Google is in a position where they're willing to continue paying the "default search engine" toll for the time being. Even their willingness to do that is compassionate, because we all know that Firefox would only harm itself by switching to another default search provider.
- Osmose 12y agoGoogle is currently working on a fix: https://bugzilla.mozilla.org/show_bug.cgi?id=1059074#c22 https://bugzilla.mozilla.org/show_bug.cgi?id=1059074#c22
- plantain 12y ago"The Firefox Nightly and beta versions have HTTP2" Seems an extremely long bow to draw when it is only affecting a tiny group of beta/nightly testers...
- snuxoll 12y agoBeta is the next release, less than six weeks and ALL FF users will be affected unless Mozilla disables it.
- dcsommer 12y agoThis is a ridiculous claim. The spec had continued to change and it is entirely understandable that there will be bugs. This is what interop testing is for. I've worked with the Google folks on the httpbis group and they are committed to the standards process.