New issue
Advanced search Search tips

Issue 890696 link

Starred by 1 user
Status: Assigned
Owner:
dullweber@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

CBD: Client hints should be deleted with cookies and history and cache

Project Member Reported by tnagel@chromium.org, Oct 1 
From https://tools.ietf.org/html/draft-ietf-httpbis-client-hints-06:

   Implementers SHOULD support Client Hints opt-in mechanisms and MUST
   clear persisted opt-in preferences when site data, browsing history,
   browsing cache, or similar, are cleared.

I'm reading this as "whenever any of ... is cleared". Ilya has confirmed that interpretation in [1].

[1] https://github.com/httpwg/http-extensions/issues/699

Comment 1 by dullweber@chromium.org, Oct 10 

Client hints currently get deleted with Cookies:
https://cs.chromium.org/chromium/src/chrome/browser/browsing_data/chrome_browsing_data_remover_delegate.cc?l=646&rcl=e12d030273549788e4f9e67c95f1d71385fde530

It might make sense to drop them with Cache as well.

Client hints are scoped to origins and not to urls, why should we delete them with history?

Comment 2 by tnagel@chromium.org, Oct 24 

> Client hints are scoped to origins and not to urls, why should we delete them with history?

Isn't origins that have been visited in the past part of the user's browsing history?
►

Sign in to add a comment