62736acb85d02f7fe6e8135a46646b7fa0e4703b: Bug 1340620 - Use inverted loading icons with Compact Theme. r=Gijs
J. Ryan Stinnett <jryans@gmail.com> - Mon, 27 Feb 2017 13:55:59 -0600 - rev 490399
Push 47088 by bmo:sledru@mozilla.com at Tue, 28 Feb 2017 11:05:49 +0000
Bug 1340620 - Use inverted loading icons with Compact Theme. r=Gijs For selected tabs, the Compact Themes use bright blue tab background colors, which makes the blue loading icon hard to see. For this state, use a white loading icon instead. MozReview-Commit-ID: 5P2VWgR4Iue
68763bfa6d054cd6bc63b61c3d127e721d8aaec8: Bug 1338215 - use a windowless browser for thumbnail hosting, r=markh
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Mon, 27 Feb 2017 19:58:55 +0000 - rev 490398
Push 47088 by bmo:sledru@mozilla.com at Tue, 28 Feb 2017 11:05:49 +0000
Bug 1338215 - use a windowless browser for thumbnail hosting, r=markh MozReview-Commit-ID: LWzMDHu0N8H
01bc4c9ad3b50d29b61e0bbfbba2862af8cf5b81: Bug 1342162 - Align pageLoad key with WebDriver; r=maja_zf
Andreas Tolfsen <ato@mozilla.com> - Thu, 23 Feb 2017 18:33:26 +0000 - rev 490397
Push 47088 by bmo:sledru@mozilla.com at Tue, 28 Feb 2017 11:05:49 +0000
Bug 1342162 - Align pageLoad key with WebDriver; r=maja_zf The WebDriver specification recently decided to use "pageLoad" instead of "page load" to identify the page load duration timeout in the session timeouts configuration object: https://github.com/w3c/webdriver/pull/796 This change aligns Marionette with WebDriver, and as long as this patch is uplifted to Aurora (53) and Beta (52) in reasonable time, we should be able to avoid the backwards compatibility dance with the Python client (for upgrade tests) because the original change to the data format landed on the current Firefox version: https://bugzilla.mozilla.org/show_bug.cgi?id=1316622 MozReview-Commit-ID: BzQeJku4AFS
3e542f18ed6278e1285cae899453679841ea5296: Bug 1337940 - Part 3 - Restrict the amount of session history we keep around during test_parse_rule. r=dbaron
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 22 Feb 2017 22:44:49 +0100 - rev 490396
Push 47088 by bmo:sledru@mozilla.com at Tue, 28 Feb 2017 11:05:49 +0000
Bug 1337940 - Part 3 - Restrict the amount of session history we keep around during test_parse_rule. r=dbaron During its run this test amasses a considerable collection of session history. Because the page title never changes, though, the Android session store previously never attempted to capture the state here. As of this bug this has changed and history change events now (correctly) trigger a session store data update on Android as well. On a debug build running on the Android emulator however, collecting the session history data can take up to 1 s when the session history count approaches the default "browser.sessionhistory.max_entries" limit of 50 entries, which increases the total running time of this test considerably and leads to timeouts (although only just). Bug 1341810 will track possibly improving the session store performance on Android by not doing a full history collect when not needed, but for the time being, restricting the amount of session history we keep around during this test is the simpler solution. MozReview-Commit-ID: JRREidiWnM3
6fa30faf379173a45cda1c400a15e4849b94013a: Bug 1337940 - Part 2 - Make session store form data test work again. r=ahunt
Jan Henning <jh+bugzilla@buttercookie.de> - Mon, 13 Feb 2017 22:16:36 +0100 - rev 490395
Push 47088 by bmo:sledru@mozilla.com at Tue, 28 Feb 2017 11:05:49 +0000
Bug 1337940 - Part 2 - Make session store form data test work again. r=ahunt Collecting data for history changes causes an additional session store data update for that tab when navigating back, which needs to be accounted for in this test. Therefore we now also wait for DOMTitleChanged before assuming that the tab has navigated to its intended location. MozReview-Commit-ID: FDNQednXPWh
4285ead0e57a8372d81dd76cf5a4182c3bd3e1fb: Bug 1337940 - Part 1 - Capture session store tab data on history listener notifications. r=ahunt
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 11 Feb 2017 21:07:29 +0100 - rev 490394
Push 47088 by bmo:sledru@mozilla.com at Tue, 28 Feb 2017 11:05:49 +0000
Bug 1337940 - Part 1 - Capture session store tab data on history listener notifications. r=ahunt So far we've simply used DOMTitleChanged as a proxy for navigation, since it's the earliest opportunity at which we have all necessary data for a new history entry (session history itself as well as tab URL and *title*) available. However it turns out that this is not 100 % reliable, since some pages might e.g. implement their navigation in JS using the history API, which won't necessarily trigger any DOMTitleChanged events. In those case we'd fail to update the tab's session history in the session store unless the user eventually navigated to someplace else that actually triggers a title change event again - if the browser was closed before that, we'd fail to properly restore the user's state. To fix this, we take a similar approach as the desktop session store and collect a tab's history data again when receiving any history change notification for that tab. Because the OnHistory... notifications are mostly cancellable, the session history hasn't been actually updated yet at the point the history listener is being called. We therefore can't synchronously call onTabLoad() from within our history change notification handler and have to schedule an async timeout instead so as to give the session history a chance to complete updating its state. MozReview-Commit-ID: LgHer940QwT
f30e28369136fcb28dddcd55a94d98e2816009e9: Backed out changeset 84a017610f03 (bug 1342427) for browser_applications_selection.js failures a=backout
Wes Kocher <wkocher@mozilla.com> - Mon, 27 Feb 2017 11:55:36 -0800 - rev 490393
Push 47088 by bmo:sledru@mozilla.com at Tue, 28 Feb 2017 11:05:49 +0000
Backed out changeset 84a017610f03 (bug 1342427) for browser_applications_selection.js failures a=backout MozReview-Commit-ID: KkzcQPJgLex
3645f65878d13fc97b1830e46d1aeb35b5967685: Bug 1343076 - enable automigration by default on early beta and earlier, r?dolske draft
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Tue, 28 Feb 2017 10:35:46 +0000 - rev 490392
Push 47087 by bmo:gijskruitbosch+bugs@gmail.com at Tue, 28 Feb 2017 10:47:21 +0000
Bug 1343076 - enable automigration by default on early beta and earlier, r?dolske MozReview-Commit-ID: 8WumBLgMUIS
a0aa14e5439de6b6acaf7d5d9ff0641730b8d231: Use simpler method of conversion and always get a null-terminated string draft
Daniel Ehrenberg <littledan@igalia.com> - Tue, 28 Feb 2017 11:39:14 +0100 - rev 490391
Push 47086 by bmo:littledan@chromium.org at Tue, 28 Feb 2017 10:40:37 +0000
Use simpler method of conversion and always get a null-terminated string MozReview-Commit-ID: ARaPZRid5EM
4052a51fcb96e2f0e4ccb69e71bd06600ec85807: Bug 1322383 - Ignore GFX sanity check window during startup of Firefox. draft
Henrik Skupin <mail@hskupin.info> - Mon, 27 Feb 2017 22:24:07 +0100 - rev 490390
Push 47085 by bmo:hskupin@gmail.com at Tue, 28 Feb 2017 10:13:40 +0000
Bug 1322383 - Ignore GFX sanity check window during startup of Firefox. On Windows systems an additional chrome window will be opened during startup. It's used for testing specific GFX related features. It's located off-screen and will usually be closed immediately. But in some situations it can take longer. To avoid an inconsistent list of start window handles Marionette should wait with starting the test until this window has actually been closed. MozReview-Commit-ID: 3k1hoSYm0Af
a18ed3fe04e95d65ef8569c4dfe5ff4b3ba07ccd: Bug 1322383 - Update Puppeteer and firefox-ui tests for valid window checks. draft
Henrik Skupin <mail@hskupin.info> - Tue, 07 Feb 2017 11:16:55 +0100 - rev 490389
Push 47085 by bmo:hskupin@gmail.com at Tue, 28 Feb 2017 10:13:40 +0000
Bug 1322383 - Update Puppeteer and firefox-ui tests for valid window checks. We have to ensure to switch to the current browser window after closing all the windows in tearDown. MozReview-Commit-ID: 3sYwmbew43d
a4325199d3e1339d8331679bb681ea407480ec66: Bug 1322383 - getCurrentWindow() has to only return the currently selected window. draft
Henrik Skupin <mail@hskupin.info> - Tue, 28 Feb 2017 11:12:39 +0100 - rev 490388
Push 47085 by bmo:hskupin@gmail.com at Tue, 28 Feb 2017 10:13:40 +0000
Bug 1322383 - getCurrentWindow() has to only return the currently selected window. Given that this method will be used in each command for checks of a valid window, we have to return the currently active window. It means the window mediator should only be used during setting up the session to find the first browser window. At the same time the code in this method is getting split-up for chrome and content scopes. MozReview-Commit-ID: KyzxYk63RgA
4b35604aefc1ca72656b930b045c8b759c245b2d: Bug 1343168 - Drop assertion when setting animation property with empty vector. r?xidorn draft
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 28 Feb 2017 19:09:17 +0900 - rev 490387
Push 47084 by hikezoe@mozilla.com at Tue, 28 Feb 2017 10:09:52 +0000
Bug 1343168 - Drop assertion when setting animation property with empty vector. r?xidorn MozReview-Commit-ID: AQSF3ltwaLd
138597ccb0c5151540753bc1f421b670ad845d9e: Bug 1322383 - Ignore GFX sanity check window during startup of Firefox. draft
Henrik Skupin <mail@hskupin.info> - Mon, 27 Feb 2017 22:24:07 +0100 - rev 490386
Push 47083 by bmo:hskupin@gmail.com at Tue, 28 Feb 2017 10:06:08 +0000
Bug 1322383 - Ignore GFX sanity check window during startup of Firefox. On Windows systems an additional chrome window will be opened during startup. It's used for testing specific GFX related features. It's located off-screen and will usually be closed immediately. But in some situations it can take longer. To avoid an inconsistent list of start window handles Marionette should wait with starting the test until this window has actually been closed. MozReview-Commit-ID: 3k1hoSYm0Af
79c68a6b1f36e81ab1429e849b94c32a676ecb70: Bug 1322383 - Update Puppeteer and firefox-ui tests for valid window checks. draft
Henrik Skupin <mail@hskupin.info> - Tue, 07 Feb 2017 11:16:55 +0100 - rev 490385
Push 47083 by bmo:hskupin@gmail.com at Tue, 28 Feb 2017 10:06:08 +0000
Bug 1322383 - Update Puppeteer and firefox-ui tests for valid window checks. We have to ensure to switch to the current browser window after closing all the windows in tearDown. MozReview-Commit-ID: 3sYwmbew43d
35aa1dc93740a360285301e17e4ba809d431410e: Bug 1322383 - getCurrentWindow() has to only return the currently selected window. draft
Henrik Skupin <mail@hskupin.info> - Tue, 28 Feb 2017 11:05:09 +0100 - rev 490384
Push 47083 by bmo:hskupin@gmail.com at Tue, 28 Feb 2017 10:06:08 +0000
Bug 1322383 - getCurrentWindow() has to only return the currently selected window. Given that this method will be used in each command for checks of a valid window, we have to return the currently active window. It means the window mediator should only be used during setting up the session to find the first browser window. At the same time the code in this method is getting split-up for chrome and content scopes. MozReview-Commit-ID: KyzxYk63RgA
5ded98f0c95830e9a6a9b7a9754acf39e84862de: Bug 276079 - add reftests to CSSWG. draft
Jeremy Chen <jeremychen@mozilla.com> - Tue, 28 Feb 2017 16:11:43 +0800 - rev 490383
Push 47082 by jichen@mozilla.com at Tue, 28 Feb 2017 08:12:23 +0000
Bug 276079 - add reftests to CSSWG. MozReview-Commit-ID: GzwgD9clZpn
614972517411847d60b5fc5f574342f174eabd40: Bug 276079 - add layout support for CSS text-justify property. draft
jeremychen@mozilla.com <jeremychen@mozilla.com> - Tue, 28 Feb 2017 16:11:42 +0800 - rev 490382
Push 47082 by jichen@mozilla.com at Tue, 28 Feb 2017 08:12:23 +0000
Bug 276079 - add layout support for CSS text-justify property. MozReview-Commit-ID: AnkF2BPXCLT
63dd05dd3de30fb899c5a3a2816a9afa73b33f4d: Bug 276079 - fix couple coding style in IsJustifiableCharacter. draft
jeremychen@mozilla.com <jeremychen@mozilla.com> - Tue, 28 Feb 2017 16:11:42 +0800 - rev 490381
Push 47082 by jichen@mozilla.com at Tue, 28 Feb 2017 08:12:23 +0000
Bug 276079 - fix couple coding style in IsJustifiableCharacter. MozReview-Commit-ID: A9tYQ85vJrK
dc1dd4090b096615f6447c647e3095a515916ac7: Bug 276079 - parse and compute CSS text-justify property. draft
jeremychen@mozilla.com <jeremychen@mozilla.com> - Tue, 28 Feb 2017 16:11:42 +0800 - rev 490380
Push 47082 by jichen@mozilla.com at Tue, 28 Feb 2017 08:12:23 +0000
Bug 276079 - parse and compute CSS text-justify property. MozReview-Commit-ID: 5OnHza5h0rX
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip