Closed hober closed 4 years ago
Seems reasonable to me and aligns with feedback I received from Chromium area owners when implementing the prompt logic. This also has some side effects that the APIs prompt also receives similar protections as other permissions w.r.t. frequent prompts and dismissals/rejections for given origin pairs on top of any explicit flags/logic we define here.
I don't think those protections are defined and given that the task source is per event loop you probably need something else to define those kind of details. (No objections to aligning these though.)
Currently we define our own
storage access request queue
. Could we use thepermission task source
instead?See also #12, #32, and w3c/permissions#206.