Update index.bs#74
Open
toreini wants to merge 1 commit into
Open
Conversation
I found this section in explainer is missing in the spec so I added it.
michaelwasserman
requested changes
May 15, 2026
| 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> |
Collaborator
There was a problem hiding this comment.
The spec's translator-permissions-policy section already covers permissions policy integration.
| <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. |
Collaborator
There was a problem hiding this comment.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I found this section in explainer is missing in the spec so I added it.
💥 Error: 422 Unprocessable Entity 💥
PR Preview failed to build. (Last tried on May 15, 2026, 12:49 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Spec Generator - Spec Generator is the web service used to build bikeshed/ReSpec specs
🔗 Related URL
Error output:
[ { "lineNum": "812", "messageType": "fatal", "text": "skipped: \"<iframe src=\"https://example.com/\" allow=\"translator language-detector\"></iframe>" }, { "lineNum": null, "messageType": "failure", "text": "Did not generate, due to errors exceeding the allowed error level." } ]This seems to be an issue with the Spec Generator service. PR Preview doesn't manage this service and so has no control over it. If you've identified an issue with it, you can report the issue to the maintainers of Spec Generator directly. Please be courteous. Thank you!
If you don't have enough information above to solve the error by yourself or if the issue doesn't seem related to Spec Generator, you can file an issue with PR Preview.