Hi
Am 13.07.2015 um 21:07 schrieb Jeff Gilbert:
> On Sun, Jul 12, 2015 at 6:45 PM, Thomas Zimmermann
> mailto:tzimmerm...@mozilla.com>> wrote:
>
> Am 08.07.2015 um 16:36 schrieb smaug:
> > Do you actually have any data how many % of Gecko devs would prefer
> > not using aFoo?
>
> I
On 7/13/15 10:36, smaug wrote:
On 07/13/2015 01:50 PM, Richard Barnes wrote:
Obligatory: Will this be restricted to secure contexts?
But given that web pages can already achieve something like this using
document.open()/close(), at least on Gecko, perhaps exposing the API
to certainly-not-sec
I would defer to the expert on the subject:
https://imgflip.com/i/o5r8m
- Kip
On 2015-07-07 6:17 PM, David Anderson wrote:
> +1 for removing this. Gecko's use is inconsistent, and outside of Gecko code
> that does use it, I've never seen it used in any other codebase. I've never
> gone to anot
On Sun, Jul 12, 2015 at 6:45 PM, Thomas Zimmermann
wrote:
> Am 08.07.2015 um 16:36 schrieb smaug:
> > Do you actually have any data how many % of Gecko devs would prefer
> > not using aFoo?
>
> I strongly prefer 'aFoo' over 'foo' for the extra context that it gives
> to the variable. If we want t
On Sun, Jul 12, 2015 at 10:45 PM, Nicholas Nethercote <
n.netherc...@gmail.com> wrote:
> On Thu, Jul 9, 2015 at 7:01 PM, Jeff Gilbert wrote:
> >
> > Arguments have the same lifetimes as locals, and the only exceptions to
> > this apply to both args and locals. (references and pointers)
>
> Maybe
I tried to get some folks internally to look at this, and so far nobody has
said that they oppose landing the changes as is very strongly so unless
there is no strong objections, I am going to ask Michael to submit his work
for landing tomorrow.
Cheers,
Ehsan
On Wed, Jul 1, 2015 at 2:54 AM, Micha
If you want to follow along, the tracking bug is https://bugzil.la/1182561
-- Forwarded message --
From:
Date: Mon, Jul 13, 2015 at 10:32 AM
Subject: [Planned ] Scheduled Tree Closing and disruptive IT Maintenance
Window, Sat July 18 2015, 0700-1400 PT
To: all-moco-m...@mozilla.co
Right now, we have a lot of in-progress responses, and not so many finished
ones. Please take 5 minutes out of your day to complete this and help
Firefox Releases improve!
Welcome to the Firefox Release Survey! This survey is anonymous, shouldn't
take more than 5 minutes, and will help us underst
On 2015-07-13 2:40 AM, Tim Guan-tin Chien wrote:
On Fri, Jul 10, 2015 at 2:45 AM, Boris Zbarsky wrote:
On 7/9/15 4:48 AM, Tim Guan-tin Chien wrote:
In this case, I modified the manifest object passed from mozApp API,
and the object was subsequently removed by the platform, so did my
modificat
Hi folks,
XULRunner is a runtime package that can be used to run XUL+XPCOM based
applications. Automated builds of it have been produced alongside
Firefox since 2006, but it has not been a supported or resourced product
for many years. We've continued to produce automated builds of it
because its
On 07/13/2015 01:50 PM, Richard Barnes wrote:
On Sun, Jul 5, 2015 at 5:11 PM, Anne van Kesteren wrote:
A while back there have been some requests from developers (seconded
by those working on GitHub) to have an API to indicate whether a site
is busy with one thing or another (e.g. networking).
On Mon, Jul 13, 2015 at 11:20 PM, Jeff Muizelaar wrote:
> I did not see nsTHashtable and nsBasHashtable define stl style
> iterators for use in range-based for loops. Is this intentional?
See https://bugzilla.mozilla.org/show_bug.cgi?id=1149833.
Nick
_
I did not see nsTHashtable and nsBasHashtable define stl style
iterators for use in range-based for loops. Is this intentional?
-Jeff
On Mon, Jul 13, 2015 at 1:36 AM, Nicholas Nethercote
wrote:
> Hi,
>
> Last week I landed patches that remove PL_DHashTableEnumerate() from
> the tree (https://bug
On Sun, Jul 5, 2015 at 5:11 PM, Anne van Kesteren wrote:
> A while back there have been some requests from developers (seconded
> by those working on GitHub) to have an API to indicate whether a site
> is busy with one thing or another (e.g. networking).
>
> They'd like to use this to avoid havin
14 matches
Mail list logo