Adam Roach a écrit :
when you look at that document, tell me what you think the parenthetical
phrase after the author's name is supposed to look like -- because I can
guarantee that Firefox isn't doing the right thing here.
In my case it does and displays : Хизер Фланаган
I have the universal
On Wed, Sep 11, 2013 at 06:49:58AM +0100, Jonathan Kew wrote:
However, several concerns regarding LZMA (lack of formal
specification combined with complexity of the code, making careful
security review and maintenance difficult; relatively slow
decompression)
Another problem with LZMA is the
On 2013-09-11, at 5:55 AM, Mike Hommey wrote:
On Wed, Sep 11, 2013 at 06:49:58AM +0100, Jonathan Kew wrote:
However, several concerns regarding LZMA (lack of formal
specification combined with complexity of the code, making careful
security review and maintenance difficult; relatively slow
On 11/9/13 14:12, Jeff Muizelaar wrote:
Brotli increases the window size and thus memory requirement to 4MB
which is quite a bit. It's also larger than the cache size on mobile
devices which is currently around 1MB so it would be interesting to
see decompression speeds on small cache devices.
On Wed, Sep 11, 2013 at 09:12:53AM -0400, Jeff Muizelaar wrote:
On 2013-09-11, at 5:55 AM, Mike Hommey wrote:
On Wed, Sep 11, 2013 at 06:49:58AM +0100, Jonathan Kew wrote:
However, several concerns regarding LZMA (lack of formal
specification combined with complexity of the code, making
On 2013-09-11, at 9:43 AM, Jonathan Kew wrote:
On 11/9/13 14:12, Jeff Muizelaar wrote:
Brotli increases the window size and thus memory requirement to 4MB
which is quite a bit. It's also larger than the cache size on mobile
devices which is currently around 1MB so it would be interesting
Hi all,
I just want to inform that I'm landing a patch that changes the DOM Promise
constructor.
DOM Promise is disabled by pref but I know that there are a few existing pieces
of code that already use them.
The old constructor was based the PromiseResolver object.
Now we get rid of this
Thus Spoke ishikawa:
On (2013年09月10日 00:08), Scott Johnson wrote:
Thus Spoke ishikawa:
So you are suggesting something like
step 1 - request for formatting a file indented in an arcane format, i.e.,
reformat it according to the currently adopted code.
Exactly what I meant, if by request for
On 9/11/13 2:13 PM, Marcos Caceres wrote:
callback PromiseInit = void (object resolve, object reject);
[Constructor(PromiseInit init)]
interface Promise {...}
What members does PromiseInit dictionary have? ^_^
It's not a dictionary. It's a callback, like the IDL snippet above says.
So
On 11/09/2013, at 6:11 PM, Andrea Marchesini amarches...@mozilla.com wrote:
Hi all,
I just want to inform that I'm landing a patch that changes the DOM Promise
constructor.
DOM Promise is disabled by pref but I know that there are a few existing
pieces of code that already use them.
On 11/09/2013, at 8:18 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 9/11/13 2:13 PM, Marcos Caceres wrote:
callback PromiseInit = void (object resolve, object reject);
[Constructor(PromiseInit init)]
interface Promise {...}
What members does PromiseInit dictionary have? ^_^
It's not a
Earlier today the backlog on Android build jobs was on the order of
1300. It seems to be coming down a little now but for a while there I
was worried it was going to grow unboundedly. Try jobs from over 10
hours ago still have pending jobs - as I'm sure you all know, having a
10-hour
Do we know why it's that much backed up? I started noticing
it yesterday. Is it because of lots of inbound pushes? lots
of try pushes? Lots of clobbering? Lots of tests?
Jim
On 9/11/13 5:31 PM, Kartikaya Gupta wrote:
Earlier today the backlog on Android build jobs was on the
order of 1300. It
quite possibly we don't need all those jobs running on tegras. I don't know of
a bug in the product that has broken on either the tegra or panda platform but
not the other.
Joel
___
dev-platform mailing list
dev-platform@lists.mozilla.org
On Wed, Sep 11, 2013 at 04:39:37PM -0700, jmaher wrote:
quite possibly we don't need all those jobs running on tegras. I
don't know of a bug in the product that has broken on either the tegra
or panda platform but not the other.
Off the top of my head:
- I have broken one but not the other
Fixing bugs like bug 884972 would probably help quite a bit. Also posting
patches with checkin info and marking the bug with checkin-needed so the
work lands with other patches. I always try to do this with simple front end
patches.
Jim
Kartikaya Gupta kgu...@mozilla.com wrote in message
2013/9/11 Mike Hommey m...@glandium.org
On Wed, Sep 11, 2013 at 04:39:37PM -0700, jmaher wrote:
quite possibly we don't need all those jobs running on tegras. I
don't know of a bug in the product that has broken on either the tegra
or panda platform but not the other.
Off the top of my
hi kats (cross-posting to dev-b2g);
tl:dr; we think all is ok again, details below. To avoid this happening
again this week, we're changing tryserver to reduce the number of
Android-tests-run-on-tegra-by-default. If you specifically want tegra
testing on tryserver, you will need to state that
18 matches
Mail list logo
