Skip to content

Fixed warnings, and made changes to the privacy considerations making it more consistent with the explainer#74

Open
toreini wants to merge 4 commits into
mainfrom
toreini-patch-explainer-spec-mismatch
Open

Fixed warnings, and made changes to the privacy considerations making it more consistent with the explainer#74
toreini wants to merge 4 commits into
mainfrom
toreini-patch-explainer-spec-mismatch

Conversation

@toreini

@toreini toreini commented May 15, 2026

Copy link
Copy Markdown
Collaborator

I found this section in explainer is missing in the spec so I added it.


Preview | Diff

I found this section in explainer is missing in the spec so I added it.
@toreini
toreini requested review from anssiko and reillyeon May 15, 2026 12:49
Comment thread index.bs Outdated
Please see [[WRITING-ASSISTANCE-APIS#privacy]] for a discussion of privacy considerations for the translator and language detector APIs. That text was written to apply to all APIs sharing the same infrastructure, as noted in [[#dependencies]].


<h3 id="iframe-privacy"> Permissions policy, iframes, and workers </h3>

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

The spec's translator-permissions-policy section already covers permissions policy integration.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Hi @michaelwasserman , sorry for the late response. It has been a bit hectic. I have two points for this change:

  1. in the spec, this is not part of privacy considerations. I think it should move there.

  2. The explainer is more comprehensive than the actual spec in describing the topic, which I think it should be minimum the other way. So I still suggest explainer and spec text should be consistent.

Comment thread index.bs Outdated
<iframe src="https://example.com/" allow="translator language-detector"></iframe>
</xmp>

These APIs are currently not available in workers, due to the complexity of establishing a responsible document for each worker in order to check the permissions policy status. See [this discussion](https://github.com/webmachinelearning/translation-api/issues/18#issuecomment-2705630392) for more. It may be possible to loosen this restriction over time, if use cases arise.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This text is already in the explainer, and the spec includes the correct Exposed=Window scope in the interface definitions.

I don't think this prose about workers and extensions is strictly needed in the spec, and isn't quite appropriate in the current form. Maybe a shorter <note> linking #18 would be appropriate.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

noted, let me think how I can address it... I will do another PR next week on this.

@toreini toreini changed the title Update index.bs Made changes to the privacy considerations making it more consistent with the explainer Jul 24, 2026
@toreini toreini changed the title Made changes to the privacy considerations making it more consistent with the explainer Fixed warnings, and made changes to the privacy considerations making it more consistent with the explainer Jul 24, 2026
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.

2 participants