1. 19 Mar, 2018 1 commit
  2. 17 Mar, 2018 3 commits
  3. 12 Mar, 2018 1 commit
  4. 11 Mar, 2018 1 commit
  5. 10 Mar, 2018 2 commits
  6. 07 Mar, 2018 1 commit
  7. 06 Mar, 2018 1 commit
  8. 05 Mar, 2018 2 commits
  9. 03 Mar, 2018 1 commit
  10. 01 Mar, 2018 2 commits
  11. 26 Feb, 2018 1 commit
  12. 24 Feb, 2018 2 commits
  13. 23 Feb, 2018 1 commit
  14. 22 Feb, 2018 4 commits
  15. 21 Feb, 2018 1 commit
  16. 18 Feb, 2018 1 commit
  17. 16 Feb, 2018 1 commit
  18. 14 Feb, 2018 1 commit
  19. 13 Feb, 2018 2 commits
  20. 11 Feb, 2018 1 commit
  21. 10 Feb, 2018 2 commits
  22. 09 Feb, 2018 3 commits
  23. 05 Feb, 2018 2 commits
    • Claudio Saavedra's avatar
      2.61.90 · 7a833921
      Claudio Saavedra authored
      7a833921
    • Michael Catanzaro's avatar
      cookie-jar: use base domain to decide if cookie is third party · 20a8463a
      Michael Catanzaro authored and Claudio Saavedra's avatar Claudio Saavedra committed
      Our third-party cookie blocking is too strict. Safari is the only major
      browser that blocks third-party cookies by default, so the only way for
      SOUP_COOKIE_JAR_ACCEPT_NO_THIRD_PARTY to be web compatible is for it to
      match Safari as closely as possible. And Safari does not appear to
      consider the full domain when deciding whether to block a third-party
      cookie, it only considers the base domain. Reports indicate that Firefox
      and Chrome behave similarly if the user chooses to block third-party
      cookies in those browsers.
      
      This fixes, in particular, notifications on google.com domains.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=792130
      20a8463a
  24. 01 Feb, 2018 3 commits