Mixed documentation on navigator.globalPrivacyControl returning 1 or true

[privacycg]

Mixed documentation on navigator.globalPrivacyControl returning 1 or true

[bvandersloot-mozilla]

https://global-privacy-control.glitch.me/ says it should return 1

This says the navigator property should be a boolean. "This value mirrors the value sent in the Sec-GPC header: it will equal true if the Sec-GPC header sent is equal to "1", and false otherwise."

Chrome returns 1
I don't believe Chrome has native support of navigator.globalPrivacyControl- how have you enabled it for your testing?

https://developer.mozilla.org/en-US/docs/Web/API/Navigator/globalPrivacyControl also indicates it isn't supported anywhere except Firefox, which seems false. They are missing the specs as well so there seems a big gap

The spec is in the See Also section. And I think among the browsers in the table, Firefox is currently the only one to support GPC without a browser extension.

[AramZS]

I agree we should make sure this is clear in the explainer: the header on the HTTP request is 1 the navigator property is true and that is the expected behavior.

[ryan-a-guthrie]

Ah ok, I do have the GPC plugin from Protegis, so that must be what is returning 1, so that would be a bug on their side according to the spec. I'm not clear if there is any overlap between this group and them, but I will send them an email.

[AramZS]

@ryan-a-guthrie Does the new text in the explainer changes in #61 explain this sufficiently clearly?

[SebastianZimmeck]

@ryan-a-guthrie, is this OK with you? If so, we we will close this issue. This resolves it for me.