28 ms·

Given the nature of the breakage (tripping over a non-w3c standard heuristic in one browser with no obvious and visible error resulting), I'd assume no engineer

Given the nature of the breakage (tripping over a non-w3c standard heuristic in one browser with no obvious and visible error resulting), I'd assume no engineer knew the code could trigger problematic behavior for some users until I see evidence of intent to the contrary.

_tulpa 8y ago
I dunno, a JS workaround for clients with third party cookies turned off seems kinda deliberate...
- deleted 8y ago
  [deleted]
- fixermark 8y ago
  Unless the workaround was done to enable Google+ functionality (responding directly to user intent to allow a +1 button click to work instead of failing with some kind of "LOL, your third-party cookies are disabled" error) and the breaking of the third-party disable heuristic as it related to general ad tracking was just an unintended side-effect.
  - quantum_magpie 8y ago
    Users don't click the +1 buttons.
  - _tulpa 8y ago
    Nobody asked for a +1 button, and I'm pretty sure you don't need 3rd party cookies to make it work anyway. Also pretty sure a company whose bread and butter is pervasive tracking doesn't break a user opt-out method by accident.