- From: Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>
- Date: Tue, 23 Jul 2013 11:35:21 +0200
- To: David Bruant <bruant.d@gmail.com>
- Cc: "Min, Hongbo" <hongbo.min@intel.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>, "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, "marcos@marcosc.com" <marcos@marcosc.com>
You are welcome to file bugs for this so that the editors can fix it when they are updating the specs Kenneth On Tue, Jul 23, 2013 at 11:23 AM, David Bruant <bruant.d@gmail.com> wrote: > 2013/7/23 Min, Hongbo <hongbo.min@intel.com> >> >> My concern is, would we unify the DOMRequest definitions and requires that >> all ongoing operation returns a DOMRequest object? In that case, it would >> make Web developer more happier since they have a consistent returning >> object for ongoing operation. > > If a unification was to happen, I hope it will be for everthing to return a > Promise http://dom.spec.whatwg.org/#promises > Worst case (need of FirefoxOS backward compat?), DOMRequest could be > reworked to inherit from Promise. But the way forward is to never use > DOMRequest ever again in a spec and use promises instead. > > Everything returning a Promise would make webdevs much happier than > everything returning DOMRequest I imagine :-) > > David -- Kenneth Rohde Christiansen Senior Engineer, WebKit, Qt, EFL Phone +45 4294 9458 / E-mail kenneth at webkit.org ﹆﹆﹆
Received on Tuesday, 23 July 2013 09:35:49 UTC