(no title)
pedrox
|
11 years ago
Does it work on Chrome (nightly or with that support enabled)?
Does anybody disagree that this is a no brainer for Mozilla: they should work that around ASAP (with a HTTP/2 blacklist for example). The impact is so high and it affects too many users.
Also note that Google in its deepest feelings wants FF down so this may by even intentional since people will always blame the client.
keeperofdakeys|11 years ago
This will simply boil down to someone not fully testing the implementation, especially since it's an extra, not a base feature. If this was an issue with Firefox stable, it would be more pronounced and worrying.
rockdoe|11 years ago
Of course they do. One less browser to support for all their properties, one annoying group in the standardization process less that keeps clamoring for annoying things like user privacy, proper spec documentation, independent implementations or god forbid, tried to oppose DRM.
If Google wouldn't want Firefox down, they wouldn't aggressively market Chrome on the search pages that Firefox users are served.
The "sponsoring" argument is totally lame. Google pays hard cash to shove their search machine down Firefox users' throat and collect the advertising dollars from it. That isn't charity.
maaaats|11 years ago
thaumasiotes|11 years ago
rockdoe|11 years ago