This patch also fixes a bug in our UpdateDropDown code where we weren't computing updated styles for <select> element, as well as another bug where we weren't passing the correct number of arguments to this.populate.
MozReview-Commit-ID: 8LAeIliRXhZ
--HG--
extra : rebase_source : 19c573ffebf700de4b4a470ceb1d2706a8088574
This looks to be happening because the binding for the checkbox may get torn down too fast when a restart is required.
MozReview-Commit-ID: 1y68jMubATx
--HG--
extra : rebase_source : 5e3277e71e771b13179b60f77352e8a5bea56d5d
This was a regression from bug 1317223. This commit also adds a
password engine sync test to catch future regressions.
MozReview-Commit-ID: 9dq8K39jLwB
--HG--
extra : rebase_source : 346c4abaf639f7781426f4e06e988c76cf552422
Ensure that six is available when running python-test tests, which
have the virtualenv python environment not that of the parent mach
process.
MozReview-Commit-ID: FrwzPZvMCSI
--HG--
extra : rebase_source : 3ce5f9d85baf8064fc547f4cd5fb94f843f7186d
We are going to need this in the future and starting collection even before releasing
Activity Stream will create a better experience once we turn it on.
And this flag is hard to miss. So let's just get rid of it.
MozReview-Commit-ID: 5oDzXhpQdSA
--HG--
extra : rebase_source : 3feea23fa614dc8a285168af0853d06417df2f35
This is a bit complicated. But most of that code should go away again as soon as
we can stop shipping the opt-out preference.
With this patch we have three flags that can be controlled via Switchboard:
* activity-stream: This is our global kill switch and allows us to pull the feature
if needed. A user has to be in this experiment to ever see activity stream. The
goal is to enable this experiment for 100% of the Nightly audience.
* activity-stream-opt-out: This is experiment will enable the Activity Stream by
default. The goal is to enable this experiment for 50% of the Nightly audience.
* activity-stream-settings: This experiment controls the visibility of a setting
to enable/disable activity stream (settings -> advanced -> experimental features).
This allows us to control whether users can opt-in or opt-out of the activity
experiment. The goal is to enable this for 100% of the Nightly audience.
MozReview-Commit-ID: BwEoTK6QMQx
--HG--
extra : rebase_source : 21f1f621160ca78d4d40f2b15f864bc111a58769
This flag wasn't used in the build system anyways. It was used to hide early builds of the
new Activity Stream UI. However this is now going to be controlled by Switchboard experiments.
MozReview-Commit-ID: Dfzw9YGgHkN
--HG--
extra : rebase_source : 2ecd3fb18a237f0de8e7d4752d69de568c062310
This makes the new client-side mapping service available from the toolbox. Note
that it's not actually _used_ from here yet, as that will happen in separately.
MozReview-Commit-ID: 5Bq774CANfC
--HG--
extra : rebase_source : f29c2e76ca4fa087e05c192fbb6e12b6fead509e
The existing `SourceMapService` uses server-side source maps, which we are
replacing with client-side source maps. It will be removed later in bug
1349354, but for now mark it as deprecated so we don't use it with any other
tools.
MozReview-Commit-ID: ABmWGC5asZd
--HG--
extra : rebase_source : 52d4238f0d4316c77fb8f4b769f84babe4d7c446
`devtools-source-map` uses `Worker` which needs a window, so it seems reasonable
to mark it as browser-based.
MozReview-Commit-ID: 93dCLoj0HDu
--HG--
extra : rebase_source : 510cdf3813b737b732c543abbcade193886b907e
Since font-language-override can only have a single three-letter tag, and it is
eventually converted to uint32_t while creating gfxFontStyle, we should be able
to move the conversion ahead, to an earlier stage.
In this patch, we move the ParseFontLanguageOverride to nsRuleNode, so we could
do the nsString-to-uint32_t conversion during computing time.
MozReview-Commit-ID: LA4Bv3wV7K
--HG--
extra : rebase_source : 48059a9913d58363f78dea59b1b7811d9f038352
nsFont::Init was created to be shared in two different constructors.
However, we could simply perform initialization in nsFont by Struct
Initialization and get the same effect.
The only primitive type that is not taken care of by nsFont::Init is
nsFont::size. Since nsFont::size represents the logical size of the font,
I think initializing it to '0' should be fine.
MozReview-Commit-ID: 6Jo7F2Bt9Sy
--HG--
extra : rebase_source : 4c440ff7345ded3586c452e3518d0da48390aa5b
These mozconfigs are no longer used since we stopped doing universal
builds in bug 1295375.
MozReview-Commit-ID: Izz9q1dRskH
--HG--
extra : rebase_source : a7b6f84d56812f0946c78aa054f116747e798300
Jared Wein
maxim
Kit Cambridge
Wes Kocher
James Graham
Mike Conley
Bobby Holley
Arshad Khan
Sebastian Hengst
Emilio Cobos Álvarez
Tom Ritter
Alexandre Poirot
Dustin J. Mitchell
Sebastian Kaspari
Dão Gottwald
Marco Bonardo ext:(%20%3Cmbonardo%40mozilla.com%3E)
J. Ryan Stinnett
Jeremy Chen
Mike Shal
Benjamin Smedberg
Gijs Kruitbosch
Carsten "Tomcat" Book