search

kyraseevers / Partitioning-visited-links-history

A proposal to partition :visited link history by top-level site and frame origin.
12 stars 1 forks source link

clarify if keying of top level site should be eTLD+1 based #2

Closed sohomdatta1 closed 1 year ago

sohomdatta1 commented 1 year ago

Based on reading https://github.com/kyraseevers/Partitioning-visited-links-history/blob/e084b3ebfc6c5183decba8aaf71c9331e11d9b6e/README.md?plain=1#L48-L56 it seems a bit unclear what a "site" means in this context. Based on the infographic, it seems to be based on the eTLD+1, but even using just keying by top level origin could potentially work here.

kyraseevers commented 1 year ago

Thanks for your question! Site here will be implemented as "schemeful site", which is eTLD+1 and scheme.

We did have some discussion of just keying by top-level origin. However, by keying by both frame origin and top-level site, it allows us to prevent sites embedded in iframes from determining the history of their embedders.