Update index.bs#74
Conversation
I found this section in explainer is missing in the spec so I added it.
| 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> |
There was a problem hiding this comment.
The spec's translator-permissions-policy section already covers permissions policy integration.
There was a problem hiding this comment.
Hi @michaelwasserman , sorry for the late response. It has been a bit hectic. I have two points for this change:
-
in the spec, this is not part of privacy considerations. I think it should move there.
-
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.
| <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. |
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.
There was a problem hiding this comment.
noted, let me think how I can address it... I will do another PR next week on this.
2 participants
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.