- From: Jeffrey Yasskin <notifications@github.com>
- Date: Thu, 21 Jul 2016 12:38:38 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Message-ID: <w3c/permissions/pull/107/c234360708@github.com>
@jan-ivar In https://github.com/w3c/permissions/pull/107#issuecomment-234170211 you asked "Are we presupposing here that UAs are barred from denying non-gesture prompts today?" The answer is "yes, UAs are barred from denying non-gesture prompts today" because there's no set of permissions states allowed by the current spec that would allow the sequence of events in https://github.com/w3c/permissions/pull/107#issuecomment-234320049. "inflict change" is a pejorative way to put it, but I'm trying to specify how browsers handle permissions in general, outside the scope of the `navigator.permissions` object (contra @marcoscaceres' answer). I think this PR makes the spec more closely align with and describe the full variance in what browsers are actually doing. @annevk I think you [captured](https://github.com/w3c/permissions/pull/107#issuecomment-234238254) one of the reasons to require user interaction with the page first: "Showing users a dialog without the user having asked for it might be confusing." Other reasons are behind the links in https://github.com/w3c/permissions/issues/77#issue-147599096. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/permissions/pull/107#issuecomment-234360708
Received on Thursday, 21 July 2016 19:39:34 UTC