nsIPluginTagInfo::getDocumentEncoding()
I don't see callers of nsIPluginTagInfo::getDocumentEncoding() in m-c. I sure hope we don't let the Java plug-in call directly into XPCOM APIs. What's this API for? Do we still need it? https://mxr.mozilla.org/mozilla-central/source/dom/plugins/base/nsIPluginTagInfo.idl#86 -- Henri Sivonen hsivo...@hsivonen.fi http://hsivonen.fi/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
RE: nsIBrowserDomWindow question
Please disregard the message I've sent earlier (below). I so far ended up not using the class. -Original Message- From: Look, Yuriy Sent: Friday, November 22, 2013 8:32 PM To: dev-platform@lists.mozilla.org Subject: nsIBrowserDomWindow question Hi, nsIBrowserDomWindow does not get recognized in C++ code, even though nsIBrowserDomWindow.h is #included. Do I need to do anything differently compare to other interfaces? Thank you in advance, Yuriy Look | Software Developer | Compuware APM yuriy.l...@compuware.com ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to replace Promise.jsm and promise.js with DOM Promises
On Thu, Nov 21, 2013 at 9:00 PM, Paolo Amadini wrote: > Though it may seem counter-intuitive, the non-native Promise.jsm has > grown better error reporting and debuggability, and maybe even better > performance (depending on whether DOM Promises are optimized for not > returning to the outer OS event loop when resolving promise chains). > > I just used the debuggability features to find a pending promise handler > that was causing a memory leak today, and I've taken screenshots: > > > https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise#Debugging > > I hope to see a comparable or even better level of debuggability in the > native Promise implementation soon! > If the original reason for using randomized variable names for storing the promise state was the inability of the debugger to inspect closures, note that this is now implemented and closed over variables can now be inspected in the debugger when execution is paused. Cheers, Panos ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
