On Wed, Jan 14, 2015 at 8:37 PM, Steve Fink sf...@mozilla.com wrote:
Why is the configure option being removed? I understand always building
unified in automation, but not having a straightforward way at all to
see if your code is buggy seems... suboptimal. If someone wants to go
through
On Wed, Feb 18, 2015 at 4:29 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 2/18/15 12:06 PM, nsm.nik...@gmail.com wrote:
1) ESR - FF 38 is an ESR release and shipping a new API with some parts
not yet supported may not be the best thing to do. What is the usual policy
in such a situation?
On Fri, Jan 2, 2015 at 7:45 PM, Xidorn Quan quanxunz...@gmail.com wrote:
On Sat, Jan 3, 2015 at 2:34 AM, c...@cemerick.com wrote:
Supporting binary keys in IndexedDB is a proposed enhancement[1] to the
standard, referred to some in the related discussion as
straightforward[2]. Chromium
On Thu, Mar 26, 2015 at 2:46 AM, Randell Jesup rjesup.n...@jesup.org
wrote:
Some examples pointed out to me: FilePicker, the spell-checker, the
DeviceStorage DOM code, DOM cache code in Manager.cpp (via
BodyStartWriteStream()), even perhaps ResolvedCallback in
ServiceWorkers. (I haven't
On Thu, Feb 19, 2015 at 11:21 AM, James Graham ja...@hoppipolla.co.uk
wrote:
On 18/02/15 17:31, nsm.nik...@gmail.com wrote:
It's still disappointing that we are implementing greenfield
web technologies with such an ad-hoc approach to obtaining
interoperability. This seems like a clear case
Actually, I'm going to steal bug 990804 and see if we can get something
worked out now. My plan is just to duplicate the STS code with a different
XPCOM uuid for now.
On Thu, Mar 26, 2015 at 9:29 AM, Benjamin Kelly bke...@mozilla.com wrote:
On Thu, Mar 26, 2015 at 2:46 AM, Randell Jesup
AM, Patrick McManus mcma...@ducksong.com
wrote:
thanks bkelly
On Thu, Mar 26, 2015 at 9:01 AM, Benjamin Kelly bke...@mozilla.com
wrote:
Actually, I'm going to steal bug 990804 and see if we can get something
worked out now. My plan is just to duplicate the STS code with a
different
XPCOM
On Wed, May 20, 2015 at 1:16 PM, Andrea Marchesini amarches...@mozilla.com
wrote:
Summary: user timing API in workers. We already have this API exposed to
main-thread content but it's nice to have it also in workers, shared
workers and service workers.
Bug:
Next week I plan to enable the Cache API by default. It has been developed
behind the dom.caches.enabled pref. This pref has been enabled by default
on nightly and aurora since FF39. Next week I plan to remove the pref
completely so the feature will ride the trains to release.
The Cache API is
Tracking protection exceptions. I wrote a bug for this last night:
https://bugzilla.mozilla.org/show_bug.cgi?id=1177641
On Fri, Jun 26, 2015 at 11:22 AM, Kyle Huey m...@kylehuey.com wrote:
On Fri, Jun 26, 2015 at 10:38 AM, Richard Barnes rbar...@mozilla.com
wrote:
Hey dev.platform
Also, I have setup a session on streams in the DOM room at Whistler:
http://juneworkweekwhistler2015.sched.org/event/28ff926a768953ba39a44cd36598d7f7
Please stop by if you have questions or just want to talk about it.
Thanks!
Ben
On Fri, Jun 19, 2015 at 2:00 PM, Benjamin Kelly bke
Streams provide a JS primitive for accessing incremental, streamed data.
For example, the fetch Response object can expose a body ReadableStream
which allows reading a potentially infinite http response. Currently the
only way to do something like this is with XMLHttpRequest with the append
:09, Benjamin Kelly wrote:
Also, I have setup a session on streams in the DOM room at Whistler:
http://juneworkweekwhistler2015.sched.org/event/28ff926a768953ba39a44cd36598d7f7
Please stop by if you have questions or just want to talk about it.
Thanks!
Ben
--
David Rajchenbach
On Fri, Jun 19, 2015 at 3:03 PM, Benjamin Kelly bke...@mozilla.com wrote:
You could also use ReadableStream, but it doesn't look as similar to
observables:
var reader = data.getStream().getReader();
reader.read().then(function handleRead(value) {
handleNext(value);
return
For the record, this landed in time for 41 here:
https://hg.mozilla.org/mozilla-central/rev/f71f5a88e16d
On Thu, Jun 18, 2015 at 11:41 AM, Benjamin Kelly bke...@mozilla.com wrote:
Next week I plan to enable the Cache API by default. It has been
developed behind the dom.caches.enabled pref
On Thu, Jul 16, 2015 at 6:28 PM, Anthony Ricaud anth...@ricaud.me wrote:
Regarding in progress|favorable|not favorable|no opinion, I think
that we don't need to be opinionated about features we aren't
implementing unless we have a firm commitment not to implement the
feature. Here I'm
16 matches
Mail list logo
