- From: Matthias Schunter (Intel Corporation) <mts-std@schunter.org>
- Date: Tue, 24 Jan 2017 09:36:31 +0100
- To: "Roy T. Fielding" <fielding@gbiv.com>
- Cc: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
Hi Roy, thanks a lot for the clarification. IMHO at this point, there is no guarantee that any of the browsers will implement the standard we propose. This means we have two choices: - We strip down the standard to whatever exists in some version of some browser. No thinking needed; look at the browser and strip the TPE spec to what is there. - We continue to evolve the standard to meet emerging (EU and other) requirements and discuss how we can demonstrate interop (e.g. by demonstrating plugins that interact with a site). My understanding is that the second option is the only one that allows us to meet our chartered goal to simplify compliance with emerging EU regulations. In this case, we are free to update anything including the JAvascript API (as long as we can then implement and validate it). Any opionions/feedback? Regards, matthias On 24.01.2017 09:15, Roy T. Fielding wrote: > Umm, the downside is that it is a normative change to the API, which means we go back to WD status and have zero implementations. > > I want commitments from browsers to implement this change before we make it. Right now we should assume the entire API will be removed. > > ....Roy > > >> On Jan 24, 2017, at 3:20 AM, Matthias Schunter (Intel Corporation) <mts-std@schunter.org> wrote: >> >> Hi Folks, >> >> >> Sites can use our javascript API to register site-wide and web-wide >> exceptions. Currently the corresponding calls do not return any results. >> >> Mike proposed to return promises. These would allow the engine to >> call-back to a site once it has processed a javascript request. This >> renders our API more asynchronous. >> >> IMHO there does not be a downside to this proposal. Mike posted the >> changed javascript API here: https://github.com/w3c/dnt/issues/12 >> >> >> Unless somebody objects before our next call, I suggest to introduce >> this change to our API. >> >> >> Regards, >> >> matthias >> >> >> >>
Received on Tuesday, 24 January 2017 08:37:04 UTC