Bugzilla

Yes, we are only collecting the counts of the host+OA.

The OA stands for OriginAttributes which is basically a set of fields that describe a context where the cookies are used. This information is used heavily to achieve distinguish and separate (partition) otherwise similar looking data. For example, you might might have cookies for any given website in multiple containers, across non/private windows or directly/from iframes.
https://searchfox.org/mozilla-central/source/__GENERATED__/__android-armv7__/dist/include/mozilla/dom/ChromeUtilsBinding.h#1097-1103

Thanks for the `./mach` tip. I'll use it next time for sure.

Yes, we are only collecting the counts, the number of cookies within each host+OA with no host+OA identifiers.

The OA stands for OriginAttributes which is basically a set of fields that describe a context where the cookies are used. This information is used heavily to achieve distinguish and separate (partition) otherwise similar looking data. For example, you might might have cookies for any given website in multiple containers, across non/private windows or directly/from iframes.
https://searchfox.org/mozilla-central/source/__GENERATED__/__android-armv7__/dist/include/mozilla/dom/ChromeUtilsBinding.h#1097-1103

Thanks for the `./mach` tip. I'll use it next time for sure.

Yes, we are only collecting the counts; the number of cookies within each host+OA with no host+OA identifiers.

The OA stands for OriginAttributes which is basically a set of fields that describe a context where the cookies are used. This information is used heavily to achieve distinguish and separate (partition) otherwise similar looking data. For example, you might might have cookies for any given website in multiple containers, across non/private windows or directly/from iframes.
https://searchfox.org/mozilla-central/source/__GENERATED__/__android-armv7__/dist/include/mozilla/dom/ChromeUtilsBinding.h#1097-1103

Thanks for the `./mach` tip. I'll use it next time for sure.