Hey Mark,
Since you've traveled this far down the rabbit hole already, seems like I
should just _casually mention_ that contributions are welcome ^_^
You can learn about Mozilla's next-gen Android browsers and browser
components here, if you're interested:
https://mozac.org/contributing/
This sounds great! I land features in the tree periodically, but
infrequently enough to forget lots of little details. It would really save
time (mine and the time of people I ping on IRC for help...) if our tooling
simplified the process of creating new tests.
I don't have any historical context
Hey all,
A big part of attracting and retaining great contributors is the tone we
set when we talk to one another.
If you see a problem and want to make things better, then you should come
up with a solution, and also do your best to communicate it effectively to
the relevant people. (Bonus
It would be great to see this info on MDN or the public wiki :+1:
On Mon, Mar 6, 2017 at 6:00 AM, wrote:
>
>
> > -Original Message-
> > From: dev-platform [mailto:dev-platform-
> > bounces+jmathies=mozilla@lists.mozilla.org] On Behalf Of Nicholas
> > Nethercote
Hi all,
I wrote a telemetry experiment last year[1], and I also found the process
challenging to navigate.
I found that many important details were undocumented, but were mentioned
in review comments, so I added what I could to the telemetry experiment
wiki page and to MDN.
My experiment
FWIW, Safari on iOS doesn't allow autoplay or preload, and also only initiates
play/load on a user-triggered event (so, pages can't use JS to fake a click).
The reason given in the docs[1] is that users might be charged for that
bandwidth.
Cheers,
Jared
[1]
Hey Edwin,
From my perspective (building service-connected Gaia apps), this proposal
makes sense: we should give developers the option of testing against real
servers.
However, I think the proposal would be improved if it described the tradeoffs
of the mock server and real server approaches,
7 matches
Mail list logo