In Firefox 43, I rewrote our Big5 support and, among other things, I
optimized the *encoder* for footprint rather than speed on the theory
that users won't notice anyway since the encoder run is followed by a
dominating wait for the network when submitting a form.
Since then, I've learned that the
(cross-posted to dev-tech-gfx and dev-tree-management, please direct
replies to dev-platform)
I just landed a change on inbound (bug 1363344) that enables various
test jobs (reftests, jsreftests, crashtests, webgl mochitests, gpu
mochitests) on the Linux64 QuantumRender (aka "linux64-qr") platform
On Tue, May 09, 2017 at 12:50:26PM +, Nicolas B. Pierron wrote:
On 05/07/2017 07:34 PM, Kris Maglione wrote:
static inline Result
WrapNSResult(PRStatus aRv)
{
if (aRv != PR_SUCCESS) {
return Err(NS_ERROR_FAILURE);
}
return Ok();
}
static inline Result
WrapNSRes
On 2017-05-10 1:05 PM, Jim Mathies wrote:
The quantum flow project has been filing a lot of bugs lately. I'm curious
about two specific whiteboard tags I've seen - [qf:p1] and [qf], can someone
explain the differences between these two tags and how this impact the priority
of these bugs?
Add
This is Jean and Harold's work documented here:
https://docs.google.com/document/d/1Ka8eNAISQodT1mS_OXapFG-_kk94GoXyo4eKH1j7EV4/edit
-- Emma
On Wed, May 10, 2017 at 8:05 PM, Jim Mathies wrote:
> Hey all,
>
> The quantum flow project has been filing a lot of bugs lately. I'm curious
> about two
Hey all,
The quantum flow project has been filing a lot of bugs lately. I'm curious
about two specific whiteboard tags I've seen - [qf:p1] and [qf], can someone
explain the differences between these two tags and how this impact the priority
of these bugs?
Thanks,
Jim
__
On Wednesday 2017-05-10 13:10 +0200, Emilio Cobos Álvarez wrote:
> On Tue, May 09, 2017 at 06:56:03PM -0700, L. David Baron wrote:
> > On Wednesday 2017-05-10 02:43 +0200, Emilio Cobos Álvarez wrote:
> > > The issue I have with per-type conventions is that it doesn't scale very
> > > well, speciall
Hey Kip,
We should probably move this to a different thread
The parent process has full privileges, so it can read whatever it wants.
As long as we express the IPC in a way that the parent can enforce rules
about filesystem access, basically so the child process doesn't use the IPC
as a gener
After some follow up investigations, it turns out the MacOS tests also rely
on this, we just hadn't noticed due to a different bug :-(
Short version: Sorry for wasting your time, you can ignore this thread.
All the other feedback we've gotten about general sandbox debugging will
still be consider
On Tue, May 09, 2017 at 06:56:03PM -0700, L. David Baron wrote:
> On Wednesday 2017-05-10 02:43 +0200, Emilio Cobos Álvarez wrote:
> > The issue I have with per-type conventions is that it doesn't scale very
> > well, specially when you're writing new code (and more specially if
> > they're not doc
10 matches
Mail list logo
