Add position on Bounce Tracking Mitigations (#961)

* Add position on Bounce Tracking Mitigations

* Added comment on cross-browser alignment.

* Wording tweak

driving implies more force than really exists

---------

Co-authored-by: Martin Thomson <mt@lowentropy.net>

activities.json

@@ -132,6 +132,19 @@
     "title": "BigInt",
     "url": "https://tc39.github.io/proposal-bigint/"
   },
+  {
+    "ciuName": null,
+    "description": "This specification defines navigational tracking and when and how browsers are required to prevent it from happening.",
+    "id": "bounce-tracking-mitigations",
+    "mdnUrl": null,
+    "mozBugUrl": "https://bugzilla.mozilla.org/show_bug.cgi?id=1839915",
+    "mozPosition": "positive",
+    "mozPositionDetail": "With 3rd-party cookies being restricted by default in all major browsers, navigational tracking plays an increasingly important role on the web. This spec describes an effective cross-browser mechanism to combat bounce tracking, which does not rely on tracker lists. It provides predictable detection heuristics for web developers and preserves legitimate uses of short-lived redirects where possible. While browsers already ship similar protections, e.g. Firefox's tracker purging, aligning on common behavior improves web compatibility and encourages site developers to use specialized APIs, rather than relying on top level redirects for functionality.",
+    "mozPositionIssue": 835,
+    "org": "Proposal",
+    "title": "Bounce Tracking Mitigations",
+    "url": "https://privacycg.github.io/nav-tracking-mitigations/#bounce-tracking-mitigations"
+  },
   {
     "ciuName": null,
     "description": "Bundled exchanges provide a way to bundle up groups of HTTP request+response pairs to transmit or store them together. They can include multiple top-level resources with one identified as the default by a manifest, provide random access to their component exchanges, and efficiently store 8-bit resources.",