On Mon, Jun 8, 2015 at 4:45 PM, Fabrice Desré wrote:
> On 06/07/2015 11:32 PM, Gabriele Svelto wrote:
> > On 08/06/2015 04:19, Greg Weng wrote:
> >> BTW, I don't know why we looks like to have no standard working model
> >> for "risky" patches. I mean, as Vivien mentioned, and what I've seen
> >>
Can't you just branch so people can continue to work as usual without any
risk to disturb your launch ?
On Sat, Jun 6, 2015 at 2:21 AM, Douglas Sherk wrote:
> Hi all,
>
> Spark is launching soon. It's based on Gaia master and Gecko
> mozilla-central, so we'd appreciate it if you avoided landing
That sounds awesome.
For master:
In the memory section there are a few strange things:
- FM Radio and Test Startup Limit USS are 0. That sounds crazy.
- Phone/Contacts RSS is close to 1.60mb that sounds crazy too.
The measures sections is empty.
Thanks for this work.
On Tue, Jun 2, 2015 at 2
As usual: Alive rocks.
On Mon, Jun 1, 2015 at 11:05 AM, Dominic Kuo wrote:
> Nice work, Alive!!!
>
> On Mon, Jun 1, 2015 at 4:47 PM, Alive Kuo wrote:
>
>> (was: Re: Improving device startup time (a.k.a. system app launch time)
>> and future work
>> in dev-gaia:
>> https://groups.google.com/for
On Thu, Feb 26, 2015 at 2:50 PM, ANTONIO MANUEL AMAYA CALVO <
antoniomanuel.amayaca...@telefonica.com> wrote:
>
> On 26 Feb 2015, at 14:31, Vivien Nicolas wrote:
>
>
>
> On Thu, Feb 26, 2015 at 12:02 PM, Antonio Manuel Amaya Calvo <
> antoniomanuel.amayaca...@
On Thu, Feb 26, 2015 at 12:02 PM, Antonio Manuel Amaya Calvo <
antoniomanuel.amayaca...@telefonica.com> wrote:
> Hi there.
>
> In the frame of the recent arguments about the permission model and making
> the apps more webby and as a result more easily updatable (or the other way
> around), we've
On 30/04/2014 00:26, Jonas Sicking wrote:
On Tue, Apr 29, 2014 at 12:58 AM, Alive wrote:
Jonas,
Thanks for clarifying, I'd filed
https://bugzilla.mozilla.org/show_bug.cgi?id=1003024 to do setVisible as
early as we could.
For a normal launched app (webapps-launch) we should do setVisible(true
On 28/04/2014 13:04, Alive wrote:
Hi,
I am not sure how does this matter if setVisible is too late or too
early while an app is launching.
The fact is while we launch an app, the previous app is still foreground
after it's going out of viewport && the foreground app is loaded.
Alive, I assu
On 24/04/2014 20:28, Kyle Machulis wrote:
b2g-desktop, the simulator, and Gaia extensions are going to merged
into one single thing: the Mulet.
So while those are 3 things currently (well 2, the Simulator has
already been merged back into b2g-desktop), there will be the same
one in the future,
distributed emulator that I'm aware of. So have
our thoughts changed on this? I was prepared to do the work then, not
sure I have time now but I do have ideas.
- Original Message -
From: "Vivien Nicolas"
To: dev-b2g@lists.mozilla.org
Sent: Wednesday, April 23, 2014 4:13
I would really like to not use any mock for integration tests. Mocks is
fine for unit tests, but does not really makes sense for integration tests.
If somone has the necessary cycles for that, I would like to push for
bug 989926, so you can use mozMobileConnection (or any RIL interfaces),
dire
As Fabrice says it does not use the gonk widget backend as this is a
desktop build.
For APZ the goal is to use it a the end. There is currently a lot of
issues with events and a few other things that prevent us to use APZ as if.
So for instance touch events are not native but simulated from m
You can file bugs on bugzilla as usual and make them blocks
https://bugzilla.mozilla.org/show_bug.cgi?id=943878
On 29/03/2014 00:50, Josh Matthews wrote:
On 03/28/2014 07:40 PM, Jonas Sicking wrote:
Mulet, french, noun. Half horse, half donkey.
Mullet, english, noun. Business in the front, par
On 19/02/2014 17:45, Jonas Sicking wrote:
On Feb 12, 2014 3:20 AM, "Vivien Nicolas" mailto:vnico...@mozilla.com>> wrote:
> On 12/02/2014 05:33, sharaf@gmail.com
<mailto:sharaf@gmail.com> wrote:
>>
>> * (As I understand) all agrees on delive
On 13/02/2014 14:48, Hugh Tay wrote:
Hello!
The code to do that, I meant. When you tap the Home button, the app
minimizes, and when you tap the app's icon again, it opens up with
its previous state preserved. But when you hold the Home button and X
the app, re-opening the app resets its state
On 13/02/2014 06:37, Alive wrote:
Vivien Nicolas mailto:vnico...@mozilla.com>> 於
2014/2/12 下午7:19 寫道：
On 12/02/2014 05:33, sharaf@gmail.com
<mailto:sharaf@gmail.com> wrote:
* (As I understand) all agrees on delivering volume key events to app
and blocking sleep and ho
On 12/02/2014 05:33, sharaf@gmail.com wrote:
* (As I understand) all agrees on delivering volume key events to app
and blocking sleep and home button at system app level.
We should definitively block the 'home' button. But for the 'sleep'
button I'm in favor of letting it goes down to th
On 17/01/2014 13:11, David Scravaglieri wrote:
Le 17/01/14 13:00, Vivien Nicolas a écrit :
What's Andrew nickname on IRC? I guess we can just spoke and figure
that out.
ahal
Merki
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
mozharness package, which seems to make sense
and saves us reinventing the wheel.
I don't know which is the best solution but I will help where I can.
On 16/01/14 11:46, Vivien Nicolas wrote:
We have already a patch that reports css warning, js errors, reflows
and can report the total memory
As I said in one other post to this thread. We will be able to cherry
pick the warning we care about directly in Gaia.
You won't see them anymore in logcat too.
On 17/01/2014 12:05, Julien Wajsberg wrote:
Le 15/01/2014 18:24, Fabrice Desré a écrit :
On 01/15/2014 09:09 AM, Julien Wajsberg wro
MOZ_INSTRUMENT_EVENT_LOOP=1.
See https://blog.mozilla.org/ted/2011/06/27/measuring-ui-responsiveness/
and
http://mxr.mozilla.org/mozilla-central/source/toolkit/xre/EventTracer.cpp#5
for more details.
On 16/01/14 07:41 PM, Vivien Nicolas wrote:
On 15/01/2014 20:48, Andrew Sutherland wrote:
However, the simplest
On 15/01/2014 19:53, James Burke wrote:
So, if there are any tools or automated reporting of errors/warnings, it
may need an exclusion list.
This is the plan as well since I want to have a tool to monitored
reflows and obviously some of them are legitimate.
This list can lived inside apps
more about that let's do a meeting.
Vivien.
On 16/01/2014 03:28, Zac Campbell wrote:
What's the ETA on that Vivien?
I've offered to work on this which make take 3-4 weeks or so but your
solution sounds like a better long term solution.
Zac
On 15/01/14 17:52, Vivien Nicolas
On 15/01/2014 20:48, Andrew Sutherland wrote:
However, the simplest/most pragmatic thing to do initially is probably
just to use the existing linux perf tool to generate logs of what's
happening during the test runs using "perf schedule" and when we see a
failure due to event loop sadness, we
On 15/01/2014 18:59, Fabrice Desré wrote:
On 01/15/2014 09:54 AM, Vivien Nicolas wrote:
I also want to expose event loop lags if possible and make them a test
failure.
That looks very dependent on the performance of the test runner. How do
we take that into account?
Performance should vary
I also want to expose event loop lags if possible and make them a test
failure.
On 15/01/2014 18:52, Vivien Nicolas wrote:
For what it worth I'm working with some devtools guys to reports JS
errors, CSS warnings and reflows to the system app. The goal is to let
us write add that as a new
For what it worth I'm working with some devtools guys to reports JS
errors, CSS warnings and reflows to the system app. The goal is to let
us write add that as a new kind of tests to Travis so people will see
that as a failure and won't be allowed to merge when doing a PR.
On 15/01/2014 18:29,
Could it be because by default mootools listen for mouse events while
the simulator use touch events ? I have no idea how mootools works, but
a quick google search told me there is a mootools mobile additional
library (the post are a bit old though).
On 13/01/2014 00:30, Matthew Hazlett wrote
Instead of restarting the phone, you can also just restart the app if
the problem is visible in an app and not in the homescreen.
On 09/01/2014 16:45, Milan Sreckovic wrote:
With the latest builds of 1.3, what you could turn on in the
developer/system menu is now the default in all builds - the
Looking at |manifest.webapp - http://pastebin.com/G6NjQxhT| you are
trying to do a certified application.
Certified and privileged application are sujects to the Content Security
Policy by default. See
https://developer.mozilla.org/en/docs/Security/CSP. As a result you can
not run inline Java
APZC has just landed turned on by default on Gaia master for eng-build.
If you already have version of Gaia running you won't see it until you
do a |make reset-gaia| or until you turn the pref on automatically.
In order to enable/disable the pref you can go in:
Settings -> Information -> More
On 10/12/2013 10:21, Bob Thulfram wrote:
On Monday, December 9, 2013 6:49:07 PM UTC-8, Bob Thulfram wrote:
Also, I thought that onXXX wasn't supported, but it seems to work. I prefer
event handlers.
onxxx (or inline JS) is not supported for privileged/certified
application due to the CSP
Would it be possible to try without using alert? It could be an error in
the way me manage modals...
On 30/11/2013 06:00, Jonas Sicking wrote:
Anonymous functions are not blocked by the CSP policy.
Only passing a string to setTimeout is blocked, but none of the examples
here do that.
What err
You likely want:
https://developer.mozilla.org/en-US/docs/Mochitest
https://developer.mozilla.org/en-US/docs/Browser_chrome_tests
Cheers,
Vivien.
On 27/10/2013 08:57, Tim Chien wrote:
Hi,
While working on DNT feature, I realized that our Gaia integration tests
(Python and JS) can only assert
http://mxr.mozilla.org/mozilla-central/source/toolkit/xre/nsAppRunner.cpp#4268
On 22/10/2013 09:16, Sam Lin wrote:
I was trying to find out where does this function get defined?
Can anyone give me a quick hint?
Thanks
___
dev-b2g mailing list
dev-b2g
window.close() likely.
On 21/10/2013 21:05, Elvis Pfutzenreuter wrote:
Is there any way for an app to close itself? I found things like
attributing a new URL to location.href, but this keeps the new
URL opened under app's "shell".
Context: if app receipt validation fails, the user needs to make
If you ever ends up with a patch for b2g/ that is front-end related feel
free to r? me. I worked a bit on this code for XUL Fennec and I will be
happy to have something for b2g.
I shared Ehsan concerns also and it would be nice if most of this code
lives in toolkit/ so it will be shared.
On
37 matches
Mail list logo
