Erik Kaplun

The last commit provides backwards compatibility in most cases (i.e. when `afterInit` does not return a `Deferred`). The change as a whole _does_ break it but then again—any code that...

I have the same problem! Only the 32772 port is being forwarded by default and I can find no hint whatsoever as to where the web interface is listening...

I realized Safari and Chrome can't open the page for some reason but Firefox can, on OS X — could that be mentioend? On Mon, Dec 7, 2015 at 3:25...

If you could only add that some browsers might not be able to connect to it (it's probably not fully standard HTTP protocol)? otherwise people might just assume the container...

My Safari and Chrome have no proxies configured... it's all standard vanilla stuff. On Tue, 15 Dec 2015 at 12:19, Jim Myhrberg [email protected] wrote: > @eallik https://github.com/eallik Are you sure...

Thanks! I'm not sure how that answers the question though...?

@Permutatrix you could mention the workaround in the "big picture" in the README for the time being, for newcomers to gulp like myself.

I'm seeing behavior where, in the "two levels" case, I get 3x full document upon initialization of the listener, then when I do a `.get('somefield').put(123)`, I get 3 invocations, only...

P.S. As a starting point, maybe just add the ability to define/add a custom little button toolbar to any content element?

any status updates on this one?