- From: Gyuyoung Kim <gyuyoung.kim@samsung.com>
- Date: Thu, 23 Feb 2012 14:24:46 +0900
- To: public-device-apis@w3.org, public-device-status@w3.org
Hello, In WebKit Bug 73528, I have implemented network info APIs based on W3C initial working draft. However, W3C adopted Mozilla's network info API proposal in the latest editor draft: - http://dvcs.w3.org/hg/dap/raw-file/84a2fb7b753b/network-api/index.html I agree with most part of the new draft. By the way, it seems Mozilla is implementing bandwidth based on empirical observation. Though I'm not sure whether that is right way, it looks good to me for now. I'm going to update existing WebKit patch based on new editor draft. P.S. There is typo: *bandwdith*. Please fix it. - Gyuyoung > -----Original Message----- > From: Mounir Lamouri [mailto:mounir@lamouri.fr] > Sent: Thursday, February 02, 2012 1:07 AM > To: public-device-apis@w3.org > Subject: Re: Network Information API: new editor draft > > On 02/01/2012 11:48 AM, Robin Berjon wrote: > > . I'm not sure that metered is such a good idea (i.e. reliable enough to > be useful), but I'll let others chime in on this. Asking the user doesn't > strike me as the best idea. > > > > . If we do keep metered, I wonder if instead of a boolean we ought to > have ""/"maybe"/"probably". > > I don't really like ""/"maybe"/"probably" because we want to tell > developers if they can use bandwidth freely or not. With unclear values, > authors will not know what to do and they might end up doing something > the user isn't expecting. > > IMO, user agents and ISP should work together to be able to give correct > values here. > > > . onchange should have a little bit of documentation. > > I believe this is done in 6.2. Also at the end of 6.1. > > Everything else has been fixed (I believe). New version is: > http://dvcs.w3.org/hg/dap/raw-file/e79e160c329e/network-api/index.html > > -- > Mounir
Received on Thursday, 23 February 2012 05:25:18 UTC