236349 2022-02-08 23:12:51 -0800 Permission API: PermissionStatus with registered "change" listeners shouldn't be GC'd 2022-02-15 09:31:12 -0800 1 1 1 Unclassified WebKit New Bugs Safari Technology Preview Unspecified Unspecified NEW https://github.com/w3c/permissions/pull/360 InRadar P2 Normal --- 229504 1 marcos webkit-unassigned cdumez marcos sihui_liu webkit-bug-importer youennf oldest_to_newest 1839027 0 marcos 2022-02-08 23:12:51 -0800 Related spec change: https://github.com/w3c/permissions/pull/360 It should be possible to get a PermissionStatus object, register a listener on it, and allow it to go out of scope (but not have it GC'd) For example: ```JS (async () => { const perm = await navigator.permissions.query({ name: "geolocation" }); perm.onchange = () => { console.log("pass") }; console.log("going out of scope"); // bye bye perm })(); // prompts for permission navigator.geolocation.getCurrentPosition(console.log); ``` Changing the permission of Geolocation in the above should produce "pass" in the developer console. 1839028 1 marcos 2022-02-08 23:15:58 -0800 Noting the works in Blink-based browsers. 1840245 2 youennf 2022-02-11 00:28:48 -0800 Right, we do not support yet onchange event handler but when it is the case, we should definitely do something about it. 1841754 3 webkit-bug-importer 2022-02-15 09:31:12 -0800 <rdar://problem/88969778>