e12cee7d872760126178afaa6b92f3ac57e495c4: Bug 1499310 - Remove moz-action URI handling from Quantum Bar. r=mak
Dão Gottwald <dao@mozilla.com> - Wed, 16 Jan 2019 17:03:53 +0000 - rev 454155
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1499310 - Remove moz-action URI handling from Quantum Bar. r=mak Differential Revision: https://phabricator.services.mozilla.com/D16683
5b6bfa47b5c4d9ac5cd655c2bb997e02776c3f60: Bug 1516768 - Put a border on add-on cards in high contrast mode r=dao
Mark Striemer <mstriemer@mozilla.com> - Wed, 16 Jan 2019 12:38:42 +0000 - rev 454154
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1516768 - Put a border on add-on cards in high contrast mode r=dao Differential Revision: https://phabricator.services.mozilla.com/D16520
34476dc321b5071bded4819e76393ca140e3472b: Bug 1520289: added TCP/DTLS/RTP/SAVPF to SDP parsing. r=bwc
Nils Ohlmeier [:drno] <drno@ohlmeier.org> - Wed, 16 Jan 2019 14:38:07 +0000 - rev 454153
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1520289: added TCP/DTLS/RTP/SAVPF to SDP parsing. r=bwc Differential Revision: https://phabricator.services.mozilla.com/D16660
d0529e2d98a3fb0259c0276e59bb70d21d782a42: Bug 1519088 - Test navigation from remote runtime to this-firefox with service workers;r=ladybenko
Julian Descottes <jdescottes@mozilla.com> - Wed, 16 Jan 2019 17:27:44 +0000 - rev 454152
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1519088 - Test navigation from remote runtime to this-firefox with service workers;r=ladybenko Depends on D16474 Differential Revision: https://phabricator.services.mozilla.com/D16475
91911f0e1e35a3965514aac9729b5641698f0243: Bug 1519088 - Remove selected runtime id from UI state;r=ladybenko
Julian Descottes <jdescottes@mozilla.com> - Wed, 16 Jan 2019 17:24:43 +0000 - rev 454151
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1519088 - Remove selected runtime id from UI state;r=ladybenko Depends on D16473 The information about the selected runtime id is duplicated between the UI state and the runtimes state. I have another stack of patches that takes the other approach, keeping this state only in the UI state. I don't have a strong opinion on which one is the best. The other stack is a bit more complicated (more refactor around runtimes-state-helper which has to read the selected runtime id from the ui state now), so I am proposing this one for now. Let me know if you'd prefer to see the other. Differential Revision: https://phabricator.services.mozilla.com/D16474
a9582642ea71edb6982f2db792cee403d58bbcea: Bug 1519088 - Add dedicated action to update selected runtime id;r=ladybenko
Julian Descottes <jdescottes@mozilla.com> - Wed, 16 Jan 2019 17:24:25 +0000 - rev 454150
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1519088 - Add dedicated action to update selected runtime id;r=ladybenko If we update the selected runtime id in a single spot, we no longer have intermediary states with no selected runtime, which was breaking the service worker action component. Differential Revision: https://phabricator.services.mozilla.com/D16473
7c46446409369b837a17aba20e550b4d6e23d683: bug 1519492 - reorganize NSSCertDBTrustDomain::FindIssuer to facilitate future improvements r=jcj
Dana Keeler <dkeeler@mozilla.com> - Tue, 15 Jan 2019 23:34:44 +0000 - rev 454149
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
bug 1519492 - reorganize NSSCertDBTrustDomain::FindIssuer to facilitate future improvements r=jcj Before this patch, NSSCertDBTrustDomain::FindIssuer would iterate over its candidate list (a CERTCertList) twice. This would have made it difficult to add in candidate issuers from other sources (see e.g. bug 1514118, wherein the goal is to bypass NSS' view of what certificates exist to facilitate third party/enterprise roots). This patch reorganizes this function to make future improvements easier. Differential Revision: https://phabricator.services.mozilla.com/D16341
793e842be7f62d5f395d7d4476850eaf53815fdc: Bug 1504659 Part 5: Update Android reftest expectations. r=botond
Brad Werth <bwerth@mozilla.com> - Wed, 16 Jan 2019 17:14:33 +0000 - rev 454148
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1504659 Part 5: Update Android reftest expectations. r=botond The tests for Bug 1133905 all compare the visibility of scrollbars with differently-sized css viewports. This patch has some affect on the viewport sizing that I don't understand, and it causes some of the tests to start passing and some to start failing. The test for Bug 1242172 has elements sized to height 100% and checking for the presence or absence of scrollbars. In this case the patch appears to increase the css viewport height and decrease the width -- again for reasons I don't understand -- and this affects the scrollbar sizes. Differential Revision: https://phabricator.services.mozilla.com/D16078
229ed2090371d4bddb1948c219e63d35767bf792: Bug 1504659 Part 4: Update tests to distinguish between layout and visual viewports. r=botond
Brad Werth <bwerth@mozilla.com> - Wed, 16 Jan 2019 17:14:03 +0000 - rev 454147
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1504659 Part 4: Update tests to distinguish between layout and visual viewports. r=botond Testing the initial value of innerWidth and innerHeight is not really viable when the visual viewport has been set by the opener, but constrained by the device. The returned value differs between the desktop and mobile browsers because of the device constraints. The simplest thing to do is to test the CSS viewport and ensure that the innerWidth values can be set. Differential Revision: https://phabricator.services.mozilla.com/D15996
0818e2b1f2c5510247c02330eb81051b04f935cc: Bug 1504659 Part 3: Add tests of viewport RDM scroll behavior, with and without touch simulation. r=gl
Brad Werth <bwerth@mozilla.com> - Wed, 16 Jan 2019 17:12:00 +0000 - rev 454146
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1504659 Part 3: Add tests of viewport RDM scroll behavior, with and without touch simulation. r=gl Differential Revision: https://phabricator.services.mozilla.com/D13174
bd806b413342b92dba5f91bd91b8f8ed2986b613: Bug 1504659 Part 2: Update innerWidth/Height getters and setters to better handle overridden visual viewports. r=botond
Brad Werth <bwerth@mozilla.com> - Wed, 16 Jan 2019 17:10:46 +0000 - rev 454145
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1504659 Part 2: Update innerWidth/Height getters and setters to better handle overridden visual viewports. r=botond Differential Revision: https://phabricator.services.mozilla.com/D15995
7c002ce6b6cc022166693ea200de66dc2ca7b811: Backed out changeset 8c88a33dc39f (bug 1519302) for failing _mozilla/binast/domain-restrict-excluded.https.html on a CLOSED TREE
Andreea Pavel <apavel@mozilla.com> - Wed, 16 Jan 2019 19:34:18 +0200 - rev 454144
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Backed out changeset 8c88a33dc39f (bug 1519302) for failing _mozilla/binast/domain-restrict-excluded.https.html on a CLOSED TREE
0f3543d470f269a834975f836adb3e5edcdb49e1: Bug 1480943 - Fix browser_webapi_theme.js TV failure. r=robwu
Luca Greco <lgreco@mozilla.com> - Tue, 15 Jan 2019 12:03:48 +0000 - rev 454143
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1480943 - Fix browser_webapi_theme.js TV failure. r=robwu This patch contains a small change needed to fix the browser_webapi_theme.js failures when it runs more then once in a row (e.g. when running in TV mode). The reason for the failure is that, when running the test more then once, by installing a new webextension theme we first receive a "lightweight-theme-styling-update" observer notification message related to the unloading on the previous theme, from the ext-theme's static unload method: - https://searchfox.org/mozilla-central/rev/b29663c6c9c61b0bf29e8add490cbd6bad293a67/toolkit/components/extensions/parent/ext-theme.js#354-356,368-370 And then another "lightweight-theme-styling-update" message related to the loading on the new theme, from the ext-theme's load method: - https://searchfox.org/mozilla-central/rev/b29663c6c9c61b0bf29e8add490cbd6bad293a67/toolkit/components/extensions/parent/ext-theme.js#101-103,119-121 To fix the failure on TV, this patch ensures that the webextension theme is uninstalled before exiting the test. Differential Revision: https://phabricator.services.mozilla.com/D16546
3e12097e2b601e2dd06b868e98bf7167c6c6aa94: Bug 1504659 Part 1: Make RefreshVisualViewportSize allow non-APZ zooming, and call it during RefreshViewportSize. r=botond
Brad Werth <bwerth@mozilla.com> - Wed, 16 Jan 2019 17:09:24 +0000 - rev 454142
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1504659 Part 1: Make RefreshVisualViewportSize allow non-APZ zooming, and call it during RefreshViewportSize. r=botond Differential Revision: https://phabricator.services.mozilla.com/D13173
7db49cc01bb7e20dc4bdb6d1a1e6a5663aa9ba98: Bug 1510566 - Document that use counters are enabled on release r=chutten
Jan-Erik Rediger <jrediger@mozilla.com> - Wed, 16 Jan 2019 16:59:40 +0000 - rev 454141
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1510566 - Document that use counters are enabled on release r=chutten Differential Revision: https://phabricator.services.mozilla.com/D16715
7f25f8bee25bcd1f5da9ef7cc8c4026560f9d356: Bug 1520368 - Clarify the queryContext.autofill property and add an enableAutofill property. r=mak
Drew Willcoxon <adw@mozilla.com> - Wed, 16 Jan 2019 17:02:26 +0000 - rev 454140
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1520368 - Clarify the queryContext.autofill property and add an enableAutofill property. r=mak This patch is based on the patch in bug 1520342. I made the UnifiedComplete provider manually check `context.enableAutofill` before setting `context.autofill`. If we end up with other providers setting `autofill`, they'd have to be careful to check `enableAutofill` too. Maybe it would be better to have a `context.autofill` getter that always returns false when `enableAutofill` is false, or a setter that forces it to be false in that case? Anyway, I opted for a simple approach in this patch. The patch also rearranges properties so that they're listed in alphabetical order. Not really necessary, but I think it's easier to pick out properties that way, and it's a logical order for adding more properties. Differential Revision: https://phabricator.services.mozilla.com/D16639
fb629855a3bbed86fb68cb7d2e42f9486f7f81be: Merge mozilla-central to autoland. a=merge on a CLOSED TREE
Razvan Maries <rmaries@mozilla.com> - Wed, 16 Jan 2019 19:06:30 +0200 - rev 454139
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Merge mozilla-central to autoland. a=merge on a CLOSED TREE
0eafc7a464331f4955977d169485c24b8b57661c: Bug 1511019 - Localize runtime name This Firefox in aboutdebugging state;r=Ola,ladybenko
Julian Descottes <jdescottes@mozilla.com> - Wed, 16 Jan 2019 16:55:37 +0000 - rev 454138
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1511019 - Localize runtime name This Firefox in aboutdebugging state;r=Ola,ladybenko This approach forces to have a new action here, but the alternative was to create the store after initializing l10n.js, which breaks all the tests because our current helper waitForRequestsSuccess is quite fragile. Differential Revision: https://phabricator.services.mozilla.com/D16455
7484d3a99bfc3de6b40f28bd1fe2c71dd456eb3f: Bug 1519917 - Consider <menulist> with sizetopopup unset equal to sizetopopup="pref" r=NeilDeakin
Timothy Guan-tin Chien <timdream@gmail.com> - Wed, 16 Jan 2019 16:30:45 +0000 - rev 454137
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1519917 - Consider <menulist> with sizetopopup unset equal to sizetopopup="pref" r=NeilDeakin sizetopopup is set to "pref" by default by the menulist XBL binding, however when converting the binding to custom element, it did not set the attribute value at a time that is early enough. This patch updates nsMenuPopupFrame and nsMenuFrame so that it considers <menulist> with unset sizetopopup attribute as equal to "pref" to avoid the problem above. This reftest layout/reftests/xul/menulist-shrinkwrap-2.xul can detect this failure. The sizetopopup attribute is never meant to be set dynamically; the fix here does not allow us to do so. Differential Revision: https://phabricator.services.mozilla.com/D16410
cbfa31396fa4b47a6162423664995167bab86c4d: Bug 1520326 - Set context.preselected when the first result is the heuristic result, regardless of result.defaultIndex. r=mak
Drew Willcoxon <adw@mozilla.com> - Wed, 16 Jan 2019 16:26:52 +0000 - rev 454136
Push 111221 by aiakab@mozilla.com at Thu, 17 Jan 2019 04:23:38 +0000
Bug 1520326 - Set context.preselected when the first result is the heuristic result, regardless of result.defaultIndex. r=mak Differential Revision: https://phabricator.services.mozilla.com/D16607
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip