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
Paolo Amadini wrote:
On 8/15/2014 3:27 PM, Neil wrote:
*SeaMonkey's search bar uses toolkit's autocomplete widget but SeaMonkey's
popup.
You're saying that it manually binds to Toolkit's autocomplete.xml?
Indeed,
http://mxr.mozilla.org/comm-central/source/suite/common/search/search.
I’m open to either options. So the current proposal is keeping tests with
external access *in the same directory* as existing tests governed by manifest
files. Good to know that adding another directory is something to avoid.
-edwin
On Aug 14, 2014, at 2:31 PM, Ehsan Akhgari wrote:
> On 20
On 8/15/2014 3:27 PM, Neil wrote:
>> It soon became apparent that most of the autocomplete code was
>> designed for synchronous operation
>>
> Synchronous operation of what? Autocomplete works like this: You ask for
> some results; some time later, you get some results. How could that be
> less syn
Paolo Amadini wrote:
It soon became apparent that most of the autocomplete code was designed for
synchronous operation
Synchronous operation of what? Autocomplete works like this: You ask for
some results; some time later, you get some results. How could that be
less synchronous?
In fact,
please note that followups are set to m.dev.platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
please note that followups are set to m.dev.platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On Wednesday, August 13, 2014 4:36:39 PM UTC+1, rvit...@mozilla.com wrote:
> I requested a public list available over NNTP (see Bug 1053202,
> mozilla.qa.telemetry-alerts). That should make everybody happy.
The list has been renamed to mozilla.dev.telemetry-alerts.
___
As part of a renewed effort to improve the user experience of location
bar searches in Firefox, we have been working on the shared code
handling search-as-you-type in textboxes [1], which is located in Toolkit.
*Current issues*
It soon became apparent that most of the autocomplete code was design
On 8/14/2014 10:05 PM, Martijn wrote:
> I think an extra column, with what kind of level style test
> (Unit/integration/UI) it is, would be nice.
I thought about this, but I think the reality is that many of those
frameworks are used for multiple type of tests, and most of the column
will end up c
On 8/14/2014 1:44 PM, Chris Mills wrote:
> I have been through the page and given it a copy edit/styling run.
Thanks a lot for that!
> Once you do decide to move it over, let me know
I've just copied the page contents over the original and set up a
redirect on the other page. Feel free to adjust
On 08/15/2014 12:03 AM, Gijs Kruitbosch wrote:
> Last I checked, AMO's review flagging tools were all regex-based. I doubt
> even issue 1 is easily regex-able. :-(
Pretty sure they do syntax checks, at least, I think using Reflect.parse, or at
least with an embedded SpiderMonkey, unsure which.
On 15/08/2014 07:17, Jeff Walden wrote:
I think our best bet is probably to evangelize the change hard,
update AMO linters to flag the issue, and (gulp) wait for, and assist
wherever possible, addon authors to update their code. Part #1,
shouldn't be too bad because they're syntax errors easily
13 matches
Mail list logo
