- From: raymeskhoury <notifications@github.com>
- Date: Wed, 27 Apr 2016 18:11:47 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Cc:
- Message-ID: <w3c/permissions/issues/86/215278758@github.com>
Thanks @annevk. I definitely agree with you that from a web developers perspective guarantees are good. However in this case, different browsers have different opinions, so it's hard to guarantee the way things should work in detail. I'm a bit worried that by defining in detail how persistent permissions work, temporary permissions work, etc. (which aren't used consistently across browsers) that the spec will become hard to follow and potentially overspecified in subtle ways. > if I have two tabs open for a given URL, those need to have access to the same permissions But this isn't necessarily true for some browser with some permissions (e.g. camera/mic on FF) and this is the intended behavior. > There need to be some reasonable guarantees to developers, otherwise the whole system is meaningless Maybe it's good to define and agree on what these guarantees are at a high level first? This might allow us to simplify what's put into the spec. This is probably hitting on some of the same things as the discussion in #83. --- 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/issues/86#issuecomment-215278758
Received on Thursday, 28 April 2016 01:12:41 UTC