bug 760193 added console.assert() method to the public web console API in Firefox 28. i'm not sure who is the primary audience for the Console.jsm API; i believe there are other, preferred methods for doing assertions in internal browser code, but at least according to some pages on mdn [1], Console.jsm is advertized to addon authors, so API parity with the apparent standard [2] seems like a good idea. https://developer.mozilla.org/en-US/docs/Tools/Browser_Console#Messages_from_add-ons https://getfirebug.com/wiki/index.php/Console.assert as a bonus, addon SDK uses devtools/Console.jsm directly to inject a global `console` object into every jetpack addon, so this fix would automatically work there too.

Thanks for the bug report. This issue is being fixed in bug 965860 where the console API is being rewritten in C++, and unified for both addons and DOM content scripts.

Chrome does this, would be nice to see it sooner rather than later.

Setting devedition-40 bugs to p3, filter on FB20EAC4-3FC3-48D9-B15F-0587C3987C25

Note, this is just for Console.jsm; not the console used in content (which has console.assert already)

(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #4) > Note, this is just for Console.jsm; not the console used in content (which > has console.assert already) d'oh, I kind of don't care then.

I'm not sure why Ember wants console.assert in Console.jsm which is only relevant to the browser toolbox. Removing from the list as its not on their current wish list AFAIK.