Unfortunately, the proposed e10s Q&A meeting conflicted with bholley's
Slaughterhouse meeting, which likely has an overlapping audience. So I
rescheduled the e10s session and you now have two awesome opportunities:
* Thursday at 10:00 AM: mconley is hosting a more front-end oriented
introducti
About recording the talk:
We will get recording gear from Rainer Cvillink and I'm happy to help
capturing the talk, but I am *terribly* inexperienced in doing this.
So any kind of help is very much appreciated!
I'll be the tall person who shows up early (my picture on the phonebook
is quite accu
+1
On Wed, Dec 3, 2014 at 5:37 PM, Seth Fowler wrote:
> Yes, looks like it is! It’s not explicitly spelled out though - someone
> searching for “initializer list”, say, won’t find it. At a minimum it seems
> worth adding an explicit mention in the text.
>
> - Seth
>
> > On Dec 3, 2014, at 2:03 P
Yes, looks like it is! It’s not explicitly spelled out though - someone
searching for “initializer list”, say, won’t find it. At a minimum it seems
worth adding an explicit mention in the text.
- Seth
> On Dec 3, 2014, at 2:03 PM, Nicholas Nethercote
> wrote:
>
> On Thu, Dec 4, 2014 at 8:54
Do you have questions about how to write and debug e10s-compatible code?
The e10s dev team will be giving an introduction to e10s and answering
your questions. Meet us Thursday afternoon from 2:00 PM – 3:00 PM in the
Medford Room (in the Marriott Waterfront basement).
chris
_
Hey Guys,
After I installed MozJpeg, under the mozjpeg/lib64/ dir, I have the following
libs:
libjpeg.a libjpeg.so libjpeg.so.62 libjpeg.so.62.2.0 libturbojpeg.a
libturbojpeg.so libturbojpeg.so.0 libturbojpeg.so.0.1.0
I am just curious:
1. if mozjpeg is just a fork of turbojpeg, why it
On Thu, Dec 4, 2014 at 8:54 AM, Seth Fowler wrote:
> So I noticed that we don’t say anything about initializer list formatting in
> our coding style guide. I’d like to propose that we standardize this
> formatting:
>
> Foo::Foo(int aBar, char aBaz)
> : mBar(aBar)
> , mBaz(aBaz)
> {
> ….
>
So I noticed that we don’t say anything about initializer list formatting in
our coding style guide. I’d like to propose that we standardize this formatting:
Foo::Foo(int aBar, char aBaz)
: mBar(aBar)
, mBaz(aBaz)
{
….
}
In other words, we should list items in the initializer list one per
This will be discussed as part of the "Async" session, on Thursday, at
Marriott, Oregon Ballroom I, Marriott Waterfront Ballroom Level.
Note a change of focus: I intend to discuss *error handling* (including
its links with test suites), rather than test suites.
Cheers,
David
signature.asc
Des
This will be discussed as part of the "Async" session, on Thursday, at
Marriott, Oregon Ballroom I, Marriott Waterfront Ballroom Level.
--
David Rajchenbach-Teller, PhD
Performance Team, Mozilla
signature.asc
Description: OpenPGP digital signature
On Wed, Dec 3, 2014 at 7:58 AM, Boris Zbarsky wrote:
> Indeed. Bringing us back to "why would someone ever care about the latter?"
I don't think you should use that unless you want to know the origin
of the URL of the corresponding href in question. E.g. similar to why
you might want to inspect
On 12/3/14, 6:30 AM, Anne van Kesteren wrote:
Correct. I thought that was added a long time ago.
location.origin has existed in Firefox since Firefox 21, I guess (and
Firefox 29 for Workers). I guess that does make it hard to remove.
That sucks. :(
Anyway, the difference between a docume
> On 2014-12-03, at 02:50, Boris Zbarsky wrote:
>
> I can't think of sane use cases for location.origin. Afaict the only reason
> it's on there is that all URLUtils things have a .origin...
I think that you will find that there are a few uses of location.origin
already. I’m willing to bet t
On Wed, Dec 3, 2014 at 11:50 AM, Boris Zbarsky wrote:
> I can't think of sane use cases for location.origin. Afaict the only reason
> it's on there is that all URLUtils things have a .origin...
Correct. I thought that was added a long time ago. Anyway, the
difference between a document's origin
On 12/3/14, 2:28 AM, Jonas Sicking wrote:
This difference seems really esoteric to me. Do we really expect developers
to understand this difference and use the right one? Especially given the
very similar names?
I don't. Hence my proposal to remove location.origin.
Are there use cases for bo
On Dec 2, 2014 1:41 PM, "Boris Zbarsky" wrote:
>
> On 12/2/14, 8:17 AM, Kevin Grandon wrote:
>>
>> We currently use location.origin quite frequently in gaia, and we also
use it in workers.
>
>
> So the difference between location.origin and document.origin is that the
latter is the origin of the d
16 matches
Mail list logo
