Setting it in your browser settings is not compatible at all. It isn't active consent by any definition of the word. It isn't per-site but set globally (hence h

Setting it in your browser settings is not compatible at all. It isn't active consent by any definition of the word. It isn't per-site but set globally (hence how it could be used to fingerprint browsers in the first place!). The header failed every possible test for actually providing any actual signal. All browsers had to do was create active consent (like they do for pop-ups, remember those?), send the appropriate header, and that is it. It would only require a few changes but the industry decided not to do that ... for whatever reason.