1193373 - Support Permissions API in Worker Context

Status: RESOLVED FIXED

(Core :: Privacy: Anti-Tracking, enhancement, P3)

Comment 2

[Andrew Sutherland [:asuth] (he/him)]

Moving this to "Privacy: Anti-Tracking" as the Permissions API is actively owned by the anti-tracking team, ex: bug 1805860, although the moz.build bugzilla component mapping should probably be updated. It's also the case that most of the design decisions for implementing this relate to architectural decisions about the Permission Manager owned by the same team since the big question is about whether the permission manager can be asked things OMT and if not, how to enhance that.

Comment 3

[Manuel Bucher [:manuel]]

Changing to worker, because this affects all workers: ServiceWorker, SharedWorker, WebWorker.

Comment 4

[Andrea Marchesini [:baku]]

Attachment: Bug 1193373 - Support Permissions API in Worker Context, r?manuel

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/ac223d01dd41
Support Permissions API in Worker Context, r=manuel,webidl,asuth,smaug

Comment 6

[Atila Butkovits]

Backed out for causing wpt failures complaining about persistent-storage.

Backout link: https://hg.mozilla.org/integration/autoland/rev/396d9a301910496ec91f2eceb513d3a5854412b2

Push where failures started: https://treeherder.mozilla.org/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=51e855a9eb6c9a0adb4247b6705099abf3d0d6e7&selectedTaskRun=IYw4c4aPRhSIaDk1wge5DA.0

Failure log: https://treeherder.mozilla.org/logviewer?job_id=477520222&repo=autoland&lineNumber=4393

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f5c51fd71f7b
Support Permissions API in Worker Context, r=manuel,webidl,asuth,smaug

Comment 8

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/mozilla-central/rev/f5c51fd71f7b

Comment 9

[Donal Meehan [:dmeehan]]

:baku could you consider nominating this for a release note? (Process info)

Comment 10

[Andrea Marchesini [:baku]]

Release Note Request (optional, but appreciated)
[Why is this notable]: Permissions API is exposed to Workers. This could fix some webcompact issue
[Affects Firefox for Android]: yes
[Suggested wording]: Support Permissions API in Worker Context
[Links (documentation, blog post, etc)]: https://w3c.github.io/permissions/

Comment 11

[Donal Meehan [:dmeehan]]

Thanks, added to the Fx133 nightly release notes, please allow 30 minutes for the site to update.
Keeping the relnote-firefox flag as ? to keep it on the radar for inclusion in the final Fx133 release notes.

Comment 12

[Donal Meehan [:dmeehan]]

Remove the relnote and clearing the relnote flag for now since this will be backed out of nightly for causing Bug 1923938
(Note: I will add the relnote back whenever this lands again)

Comment 13

[Serban Stanca [:SerbanS]]

Backed out for causing as requested by dmeehan for causing Bug 1923938.

• Backout link

Comment 14

[Pulsebot]

Backout by [e-mail]:
https://hg.mozilla.org/mozilla-central/rev/9b02297ce840
Backed out changeset f5c51fd71f7b as requested by dmeehan for causing Bug 1923938. CLOSED TREE

Comment 16

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/b3523163404b
Support Permissions API in Worker Context, r=manuel,webidl,asuth,smaug

Comment 17

[BugBot [:suhaib / :marco/ :calixte]]

Copying crash signatures from duplicate bugs.

Comment 18

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/b3523163404b

Comment 19

[Donal Meehan [:dmeehan]]

Added the relnote back to the FX133.0a1 notes
Keeping the relnote-firefox flag as ? to keep it on the radar for inclusion in the final Fx133 release notes.

Comment 20

[Hamish Willee]

FF133 MDN docs work for this tracked in https://github.com/mdn/content/issues/36530. This was just a release note and browser compatibility update.

Comment 21

[Donal Meehan [:dmeehan]]

Added to the Fx133 release notes.
Available to preview on staging, please allow 30 minutes for the site to update.