Skip to content

Conversation

@dotproto
Copy link
Contributor

This PR introduces a new section titled "Terminology in consent prompts" to provide developers with additional guidance on the expected presentation of data transmission consent prompts.

Screenshot of this PR's changes as they appear on a local development server.

@fjosephmoz
Copy link

LGTM

@dotproto dotproto requested a review from willdurand December 19, 2025 14:20
Copy link
Member

@willdurand willdurand left a comment

Choose a reason for hiding this comment

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

r+wc

| Personal | "personal data"<br>"personal information"<br>"personally identifying information" |
| Technical & Interaction | "technical data"<br>"anonymous data"<br>"user interaction data"<br>"technical and user interaction data" |

We generally prefer that extensions follow this convention as consistent
Copy link
Member

Choose a reason for hiding this comment

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

I believe this shouldn't be hard wrapped but that's a nit

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do you mean the use of <br> here? AFIAK markdown tables don't allow line breaks inside cells, so we have to fall back to HTML to get the desired effect.

Copy link
Member

Choose a reason for hiding this comment

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

no, the paragraph after the table. we don't wrap at 80 chars or so.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah, thanks, I'll fix that.

@dotproto dotproto merged commit 9b918d5 into mozilla:master Dec 19, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants