All connections to mozqa.com which do not use SSL have to be done
to a unique subdomain. This was requested to lower the amount of
active HTTP endpoints.
MozReview-Commit-ID: JAFjQFhTCxT
--HG--
extra : rebase_source : 7f584f4a3848b122eadd6e25799d43718352a03d
To allow update tests to use source builds of Firefox before bug 1355888
was landed, the MOZ_MARIONETTE environment variable has to be be
pre-emptively set. Otherwise Marionette will not be activated after
the update has been applied.
MozReview-Commit-ID: Hqb6SjYtOPR
--HG--
extra : rebase_source : 10f9b4d2545198fc95294381ec1db63f1445c736
Continue to allow non-multiprocessCompatible extensions in automation.
There are a ton of places that would need to be changed, many of which
will be changing soon anyway with the non-webextensions change in 57
so this is mostly the expedient route to keeping the tree green.
MozReview-Commit-ID: EZZoDVdhLfy
--HG--
extra : rebase_source : f83472bc1c88dd0deadbe485d9002499027ff07f
Continue to allow non-multiprocessCompatible extensions in automation.
There are a ton of places that would need to be changed, many of which
will be changing soon anyway with the non-webextensions change in 57
so this is mostly the expedient route to keeping the tree green.
MozReview-Commit-ID: EZZoDVdhLfy
--HG--
extra : rebase_source : 34aa762917566b052ade6372280caed72fbfbe9a
The unit tests for the software update class should not rely on
the remote update URL being reachable. Instead a locally served
URL has to be used.
MozReview-Commit-ID: 8WNoEb0PUWz
--HG--
extra : rebase_source : 85900716de5c868efd8f0411e0c577f317d98d25
To ensure that we correctly restart Firefox for update tests, the restart
button in the about window or the old software update window have to be
clicked.
MozReview-Commit-ID: 7acl1DcA85d
--HG--
extra : rebase_source : 8af6c300ae34befc2c05e801ea4b5901659c1c2a
Updates consumers to the new behavior.
Some consumers are changed to use the "page-icon:" protocol, since it's not
trivial to join the icons table and get a single result out of it. In most cases
the join would return multiple results since a page can have multiple icon payloads.
These consumers for now will return the biggest payload, bug 1347532 will fix
some of them to properly pass a #size=NN fragment.
Note that, even before, these were just "moz-anno:favicon:" uris, and the
payload had to be fetched from the database.
Some other consumers for now just fallback to the largest payload, by passing 0
to GetFaviconURLForPage.
The favicon optimization still happens on the main-thread, bug 1346139 will
handle that problem.
Most of the changes involve handling the modified IconData objects, that now
retain an array of payloads, rather than just one. But note that .ico files are
not yet split into single frames, due to imagelib missing APIs that will be handled
in bug 1337402.
The other changes involve fixing queries to properly join with the new tables.
Finally, note that thanks to the FOREIGN KEYS support, removing from moz_icons or
moz_pages_w_icons will also remove relations from moz_icons_to_pages.
The system only supports square icons, so icons are resized based on their larger side.
This doesn't include new tests, those will be in a following changeset.
MozReview-Commit-ID: JUkpquhpS8y
--HG--
rename : toolkit/components/places/tests/unit/test_svg_favicon.js => toolkit/components/places/tests/favicons/test_svg_favicon.js
extra : rebase_source : fa49c4a81d6ab6b34a2f19ee4175e889a6e9d734
As long as update tests do not support the new simplified update ui
it has to be kept disabled.
MozReview-Commit-ID: 4fC0CYhp7Pc
--HG--
extra : rebase_source : f3558973b0153fe2104f0e612120298d711fc491
To ensure better failure messages a refactoring of checks has to be done. It
includes the following changes:
* No further checks for a follow-up (watershed) update. It's not supported
and as such doesn't need assertions (bug 1353717)
* Checks for fallback updates have to be made to ensure that an invalidated
partial/complete update does not cause an upgrade of Firefox during the restart.
MozReview-Commit-ID: CLb0aXoIur2
--HG--
extra : rebase_source : e41f2463cef695f6f9984ea2ee6f7d43196a9138
There was never a need to run a multiple-update step in the past, and as
we agreed a while ago it is not something we want to do in the future.
It means that watershed releases will have to be tested by issuing
multiple update tests.
MozReview-Commit-ID: 7cmK3gEOkv1
--HG--
extra : rebase_source : dac6bcf5d4505febc9b6ffb6333cf77b41d4dc4a
There is no need to close this dialog given that a restart happens anyway.
But doing that as right now, and trying to invoke execute_script() on it,
will end up with a unlocatable window.
MozReview-Commit-ID: 53yBLYsWX4o
--HG--
extra : rebase_source : 21b02231c845cf994c7c75d10bd91e0911114998
We have to ensure to switch to the current browser window after closing all the windows
in tearDown.
MozReview-Commit-ID: 3sYwmbew43d
--HG--
extra : rebase_source : 6afb6430c40d7b248320cae95ddef4ace86b0042
We have to ensure to switch to the current browser window after closing all the windows
in tearDown.
MozReview-Commit-ID: 3sYwmbew43d
--HG--
extra : rebase_source : d1ad51ed5fafb875fcc055f582ce6df17b48a2d2
We have to ensure to switch to the current browser window after closing all the windows
in tearDown.
MozReview-Commit-ID: 3sYwmbew43d
--HG--
extra : rebase_source : 1c37bc56d33e753a29f7f8242b87d224015b4a20
We have to ensure to switch to the current browser window after closing all the windows
in tearDown.
MozReview-Commit-ID: 3sYwmbew43d
--HG--
extra : rebase_source : d5514b59af6ce7185e000107be021db6d6118b65
As it has been turned out setting the desired update channel via a preference
on the default branch does not work. Instead it really has to be set in the
channel-prefs.js file.
If not done so, the updater will see the new channel as invalid and abort the
update process.
MozReview-Commit-ID: 6NqYaijAcsX
--HG--
extra : rebase_source : 31f3da79c960ca68b715df4b7cf70e4d486a2281
It should not be possible to close a background tab via the menu shortcut.
Instead another method should be used, best here is the close button.
MozReview-Commit-ID: 3cZmAyPsnj7
--HG--
extra : rebase_source : 83890072d5763bd562bbf69c9ac79c094ae14b84
Cookie handling should be restricted to content scope and will be
enforced with a following patch. This patch fixes the unit test.
MozReview-Commit-ID: LpbBMH5refy
--HG--
extra : rebase_source : f94dfc382589358b054688fbaa2caab0b937f4da
Fix for a regression as introduced by bug 1277090. get_attribute() no longer returns
values of Element properties. For the latter get_property() has to be used now.
MozReview-Commit-ID: K45rcHDM6YC
--HG--
extra : rebase_source : d35ea60aa41fad0e84c967cd1042c61106f9a442
Fix for a regression as introduced by bug 1277090. get_attribute() no longer returns
values of Element properties. For the latter get_property() has to be used now.
MozReview-Commit-ID: K45rcHDM6YC
--HG--
extra : rebase_source : 8ca27167b364832a99c29eb9cf1f16181493d950
Marionette's skip decorators are currently not conform with the ones from the
Python's unittest module, which require a reason as parameter. As such Marionette
should behave the same and should also require a reason for more detailed skip
messages. This is done by wrapping the actual decorator with another enclosing
method.
With the changes we also ensure that the wrapper has the same attributes as the
wrapped function by using functools.wraps(). This hasn't used so far and makes
debugging harder.
Further a couple of skip methods and classes were copied from the unittest module,
which should be better imported instead to reduce code duplication.
MozReview-Commit-ID: 6XT6M6cbCFW
--HG--
extra : rebase_source : 2fb8bce0f17eade182eb5f61479548d0f6ef8ecc
Geoff Brown
Henrik Skupin
Ryan VanderMeulen
CuriousLearner
Raajit Raj
Andrew Swan
Sebastian Hengst
Marco Bonardo
Francois Marier
Wes Kocher
ui.aseem_yadav
Carsten "Tomcat" Book
Thomas Nguyen
Gabor Krizsanits
Dão Gottwald
Henry Chang