Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft language to address font fingerprinting mitigation (#1202). #1210

Merged
merged 1 commit into from
Feb 17, 2021

Conversation

skynavga
Copy link
Collaborator

Closes #1202.

Copy link
Contributor

@nigelmegitt nigelmegitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me, though I have added one fairly minor grammatical nit. I think it matches where we got to in https://www.w3.org/2020/07/27-tt-minutes.html#t02 i.e. it is a helpful change, but we may need more later, after further consideration.

spec/ttml2.xml Show resolved Hide resolved
<note role="example">
<p>As an example, a mitigation strategy can involve ignoring user-installed <loc href="#terms-font-resource">font resources</loc>
when choosing whether to dereference (download) <loc href="#terms-font-resource">font resources</loc>.</p>
</note>
<p>Implementations of a <loc href="#terms-content-processor">content processor</loc> in the context of a <emph>general purpose browser</emph>,
as that term is used by <bibref ref="finger"/>, should consider not dereferencing external font resources conditionally in the presence

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be better to say "...should not dereferencing external font resources...". The addition of "consider" weakens the strong recommendation.

@css-meeting-bot
Copy link
Member

The Timed Text Working Group just discussed Draft language to address font fingerprinting mitigation (#1202). w3c/ttml2#1210, and agreed to the following:

  • SUMMARY: Andreas's proposal to be applied
The full IRC log of that discussion <nigel_> Topic: Draft language to address font fingerprinting mitigation (#1202). #1210
<nigel_> github: https://github.com//pull/1210
<nigel_> Nigel: I reviewed this (opened since July), and think it is an improvement and a step on the way but maybe not the end of the changes we need.
<nigel_> Andreas: I added one comment to the pull request where the addition is to strongly recommend not to dereference external fonts.
<nigel_> .. In the current pull request it says "should consider not dereferencing"
<nigel_> .. I think the "consider" should be removed.
<nigel_> .. The reasoning is that we had a long discussion with PING, who asked for more, they wanted it normative.
<nigel_> .. It is now strong language in a non-normative section.
<nigel_> .. I think we should not weaken it more, and it would be better to say "should not do it".
<nigel_> Nigel: I think Glenn already indicated he would accept it, and I certainly would.
<nigel_> Glenn: I don't like it but I could live with it.
<nigel_> Nigel: I can't see Andreas's comment on the pull request, only my proposal.
<nigel_> Andreas: I commented it but I maybe need to complete the review.
<nigel_> Nigel: If we make that change then my change would not be needed.
<nigel_> .. I would like to merge this - any requests for more time to review?
<nigel_> group: [no requests for more time]
<nigel_> Nigel: In that case when Andreas's change has been processed we should be good to merge.
<nigel_> SUMMARY: Andreas's proposal to be applied

Base automatically changed from master to main February 5, 2021 09:24
@skynavga skynavga merged commit 2499711 into main Feb 17, 2021
@skynavga
Copy link
Collaborator Author

Merge per request from @nigelmegitt in order to advance to new CR.

@skynavga skynavga modified the milestones: 2ED-PR, 2ED-CR2 Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CSS font-matching algorithm may introduce fingerprinting issues
4 participants