Thanks for sharing discussion notes! It's been mentioned a couple of times in passing on recent calls the possibility of altering the Exception API to be asynchronous, so that a site could call it and only later get back a response (based on user input through browser chrome, for example). I wanted to remind the group that we had previously had the API as asynchronous when it was expected that it was the browser that was asking the user, but we made the decision (based on feedback from both browsers and sites) that sites would obtain consent from the user directly and that the exception API was simply about storing an exception. As a result, it is intentionally synchronous. Sites have to accommodate that users may change their decision at a later time, but we don't need separate Promises to handle that situation. I believe we responded to TPE Last Call comments to that effect. I would suggest that we not re-open this issue. Cheers, Nick > On Sep 22, 2016, at 8:35 AM, Matthias Schunter (Intel Corporation) <mts-std@schunter.org> wrote: > > Hi TPWG Group, > > > enclosed are slides that we compiled while discussing TPE today. > Feedback is welcome! > > > matthias > <W3C-TPAC-TPWG-Meeting-v02.pptx>
Received on Monday, 26 September 2016 02:22:27 UTC