On Fri, Feb 9, 2018 at 2:05 PM, Henri Sivonen wrote:
> On Fri, Feb 9, 2018 at 12:00 PM, Emilio Cobos Álvarez
> wrote:
>> On 02/09/2018 10:49 AM, Henri Sivonen wrote:
>>> Is there some trick to make gkrust compilation succeed on a 32-bit system?
>>
>> The BSD folks seem to be using --disable-debu
On Mon, Feb 26, 2018 at 7:02 PM, Brian Grinstead wrote:
> console.assert doesn't throw an exception, and neither does NS_ASSERT. So I
> don’t think replacing consumers with exceptions is correct if we want to keep
> the current behavior. But I guess the intent for places code in bug 1431050
> i
+1 Please make NS_ASSERT die.
On Mon, Feb 26, 2018 at 09:37:09AM -0800, Brian Grinstead wrote:
There have been some improvements to the console API for chrome callers
recently:
* The WebIDL implementation is available as a global in JSMs - no need to
import Console.jsm (bug 1425574)
* Chrome
console.assert doesn't throw an exception, and neither does NS_ASSERT. So I
don’t think replacing consumers with exceptions is correct if we want to keep
the current behavior. But I guess the intent for places code in bug 1431050 is
to change the behavior and make those assertions throw? If that
We were already working with a contributor to remove NS_ASSERT and debug.js in
https://bugzilla.mozilla.org/show_bug.cgi?id=1431050 and we were just
replacing those few calls with simple exceptions.
The usage is not particularly spread in the codebase and the benefits
in ruining Nightly testers lif
There have been some improvements to the console API for chrome callers
recently:
* The WebIDL implementation is available as a global in JSMs - no need to
import Console.jsm (bug 1425574)
* Chrome console API calls print to stdout if "browser.dom.window.dump.enabled"
is true (bug 1439686)
* `c
Ah, I missed that Mike had replied -- it sounds like archive.org's
Wayback Machine is the easier way to get at the study, as compared to
bothering Josh. :)
On 2/26/18 9:26 AM, Daniel Holbert wrote:
> The people.mozilla.org site was a general-purpose webserver for Mozilla
> folks, and it was decomm
The people.mozilla.org site was a general-purpose webserver for Mozilla
folks, and it was decommissioned entirely over the past few years. So,
that's why the study link there is broken.
You'd have to ask Josh (CC'd) if he has reposted (or could repost) the
study docs somewhere else.
~Daniel
On
Hello,
Here's the list of new issues found and filed by the Desktop Release QA team
last week.
Additional details on the team's priorities last week, as well as the plans for
the current week are available at: https://goo.gl/yxTYxJ
Bugs logged by Desktop Release QA in the last 8 days
Core: Pri
9 matches
Mail list logo
