8081a895e435: Bug 1393402 - Set longer timeout for document load. r=mixedpuppy, a=test-only on a CLOSED TREE DEVEDITION_56_0b7_RELEASE FENNEC_56_0b7_BUILD1 FENNEC_56_0b7_RELEASE FIREFOX_56_0b7_BUILD2 FIREFOX_56_0b7_RELEASE
Shane Caraveo <scaraveo@mozilla.com> - Thu, 24 Aug 2017 14:35:31 -0700 - rev 421463
Push 7687 by ryanvm@gmail.com at 2017-08-28 18:53 +0000
Bug 1393402 - Set longer timeout for document load. r=mixedpuppy, a=test-only on a CLOSED TREE MozReview-Commit-ID: BSWPMaNvtwG
2968e01b6f20: Bug 1390346 - Test jar caching in combination with redirects. r=rpl, a=lizzard
Shane Caraveo <scaraveo@mozilla.com> - Fri, 18 Aug 2017 10:59:44 -0700 - rev 421462
Push 7687 by ryanvm@gmail.com at 2017-08-28 18:53 +0000
Bug 1390346 - Test jar caching in combination with redirects. r=rpl, a=lizzard MozReview-Commit-ID: 6sFdcruieh6
e9c83e49ec46: Bug 1390346 - Redirects to moz-extension:-URLs fail when loaded from a xpi. r=jimm, a=lizzard
Haik Aftandilian <haftandilian@mozilla.com> - Fri, 18 Aug 2017 11:30:21 -0700 - rev 421461
Push 7687 by ryanvm@gmail.com at 2017-08-28 18:53 +0000
Bug 1390346 - Redirects to moz-extension:-URLs fail when loaded from a xpi. r=jimm, a=lizzard MozReview-Commit-ID: 2FzUWLTiLs
bc8f7e510cc8: Bug 1366603 - Wait for rAF before waiting the MozAfterPaint in test_deferred_start.html. r=hiro, a=test-only
Mantaroh Yoshinaga <mantaroh@gmail.com> - Mon, 28 Aug 2017 08:01:31 +0900 - rev 421460
Push 7687 by ryanvm@gmail.com at 2017-08-28 18:53 +0000
Bug 1366603 - Wait for rAF before waiting the MozAfterPaint in test_deferred_start.html. r=hiro, a=test-only This test called waitForPaints() after creating an animation, but waitForPaints() didn't wait for a MozAfterPaint event actually since DOMWindowUtils.IsMozAfterPaintPending which is checked a MozAfterPaint event has been queued return false[1]. (i.e. This test didn't wait for a MozAfterPaint) This is related to bug 1341294. If gecko can receive a MozAfterPaint corresponded to own paint, waitForPaint() does not need to check for DOMWindowUtils.IsMozAfterPaintPending. This patch is a workaround until bug 1341294 is resolved. [1] http://searchfox.org/mozilla-central/rev/5696c3e525fc8222674eed6a562f5fcbe804c4c7/testing/mochitest/tests/SimpleTest/paint_listener.js#60 MozReview-Commit-ID: 6Rnv8MBP6Se
02852b5a5b3c: Bug 1390816 - Part 1: Add addresses sync checkbox in first time saving doorhanger. r=lchang, a=lizzard, l10n=flod
steveck-chung <schung@mozilla.com> - Wed, 16 Aug 2017 19:08:32 +0800 - rev 421459
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1390816 - Part 1: Add addresses sync checkbox in first time saving doorhanger. r=lchang, a=lizzard, l10n=flod MozReview-Commit-ID: KkpseMw4kRk
6a38cf9003c6: Bug 1393063 - Part 1: Fix IPCStreamSource's handling of async streams returning 0 from Available. r=bkelly, a=lizzard
Boris Zbarsky <bzbarsky@mit.edu> - Tue, 13 Jun 2017 16:16:55 -0400 - rev 421458
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1393063 - Part 1: Fix IPCStreamSource's handling of async streams returning 0 from Available. r=bkelly, a=lizzard This aligns the code more closely with how the input stream pump works: 0 available bytes when the stream itself told us it's ready means the stream is at the end. Note from asuth: This fix was originally part of bug 1371699, it was part 5. However, its initial landing was backed out, but it is now very much needed for bug 1393063, so I'm landing it.
b185b492e4ee: Bug 1391645 - Make nsPrintEngine::SetupToPrintContent() proceed with the print even when mPrt->mPrintObject->mPresShell and mPrt->mPrintObject->mPresContext are nullptr but mIsCreatingPrintPreview is false. r=dholbert, a=lizzard
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 21 Aug 2017 14:56:07 +0900 - rev 421457
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1391645 - Make nsPrintEngine::SetupToPrintContent() proceed with the print even when mPrt->mPrintObject->mPresShell and mPrt->mPrintObject->mPresContext are nullptr but mIsCreatingPrintPreview is false. r=dholbert, a=lizzard Bug 1376693 added a null-check to bail from print operations if mPresShell/mPresContext are null, to avoid some null-deref crashes. However, it turns out it's possible for these variables to be null under normal conditions -- for example, when nsPrintEngine is printing documents, mPrt->mPrintObject->mPresShell and mPrt->mPrintObject->mPresShell can be nullptr if the document has <frameset> element and it's printing only content of a <frame> element or all <frame> elements separately. This special frameset-printing mode can cause these variables to be null; however, the crash occurred only when mIsCreatingPrintPreview is true. So, we should check the variables only when it's true. Fortunately: * the null-deref crashes that Bug 1376693 wanted to avoid were all in code that we only visit when mIsCreatingPrintPreview is true (i.e. during print preview). * this special frameset-printing mode (which causes these variables to be null) _cannot be used during print preview_. So, we can avoid the print-preview-specific crashes without breaking frameset-printing by simply making our null-check bail-out conditional on mIsCreatingPrintPreview. MozReview-Commit-ID: FJ3ynrXTxnI
e08568b12c29: Bug 1391628 - Use fallback locale on nsICollation if locale is invalid. r=emk, a=lizzard
Makoto Kato <m_kato@ga2.so-net.ne.jp> - Thu, 24 Aug 2017 23:13:42 +0900 - rev 421456
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1391628 - Use fallback locale on nsICollation if locale is invalid. r=emk, a=lizzard Original issue is that Microsoft Dynamics CRM uses invalid lang attribute in <xsl:sort>. <xsl:sort order="descending" select="@displayname[$sortColumnName='displayname'] | @name[$sortColumnName='name'] | exslt:node-set($FriendlyTypeNames)/types/type[@xmlName=current()/@datatype and $sortColumnName='datatype']" lang="$languageName"/> Our XSLT implementation detects "$languageName" as locale name, then use it to nsICollation. Until Gecko 54 for Windows, even if using invalid locale name for nsICollation, it uses platform locale as fallback. But from 55, we use same implementation as macOS's to use ICU. So this issue occurs. ICU implementation doesn't use fallback locale if it is invalid. We should use fallback locale if locale is invalid. Most code for fallback locale such as FallbackEncoding uses application locale, so use it. MozReview-Commit-ID: EKYkZG7Hnz0
b20ed3e70390: Bug 1391857 - Fix ctx flags for e10s stun addr gathering. r=drno, a=lizzard
Michael Froman <mfroman@mozilla.com> - Tue, 22 Aug 2017 10:13:06 -0500 - rev 421455
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1391857 - Fix ctx flags for e10s stun addr gathering. r=drno, a=lizzard In the case of e10s, the ctx flags for default route only (and less importantly in this case, proxy only) were not set on the ice ctx when SetStunAddrs was called in PeerConnectionMedia. MozReview-Commit-ID: CldUpJfaaH3
e070c1cca1be: Bug 1347518 - Part 2: Don't attempt to determine frame type when encrypted. r=cpearce, a=lizzard
Jean-Yves Avenard <jyavenard@mozilla.com> - Mon, 21 Aug 2017 18:54:44 +0200 - rev 421454
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1347518 - Part 2: Don't attempt to determine frame type when encrypted. r=cpearce, a=lizzard The data being encrypted, is nonsensical. So we always rely on the container information MozReview-Commit-ID: 4uQ9l3Q1Ebl
fb8967e983b1: Bug 1347518 - Part 1: Use SEI recovery point to mark keyframe. r=jesup, a=lizzard
Jean-Yves Avenard <jyavenard@mozilla.com> - Mon, 21 Aug 2017 18:34:38 +0200 - rev 421453
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1347518 - Part 1: Use SEI recovery point to mark keyframe. r=jesup, a=lizzard Some streams do not include any IDR frames. However, they do include SEI recovery point markers. We use those to mark keyframes. MozReview-Commit-ID: IHfUx7fEgEJ
9e2fda5c1b95: Bug 1392322 - Fix browserAction.setTitle for currently active tab on Android. r=mixedpuppy, a=lizzard
Luca Greco <lgreco@mozilla.com> - Mon, 21 Aug 2017 19:16:46 +0200 - rev 421452
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1392322 - Fix browserAction.setTitle for currently active tab on Android. r=mixedpuppy, a=lizzard MozReview-Commit-ID: 1Wka0zFxElD
fa9cdc61ccc2: Bug 1391770 - Don't allow a faraway second tap to start a one-touch-pinch gesture. r=botond, a=lizzard
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 19 Aug 2017 08:50:55 -0400 - rev 421451
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1391770 - Don't allow a faraway second tap to start a one-touch-pinch gesture. r=botond, a=lizzard This patch adds a new tolerance pref, which controls how far the second touchdown is allowed to be from the first touchdown when detecting a multi-tap gesture such as double-tap or one-touch-pinch. This stops the one-touch-pinch code from inadvertently triggering when the user does a tap followed by a second tap far away from the first. The default value for the new pref is 5x the touch-start tolerance pref. This seems to provide a reasonable behaviour for me, although this value could probably be tuned. MozReview-Commit-ID: 63aAyGCbvoN
8b4fbaa0a0de: Bug 1388152 - Save abbreviated state name of address-level1 select element rather than its value in form autofill submission. r=lchang, r=MattN, a=lizzard
Ray Lin <ralin@mozilla.com> - Mon, 14 Aug 2017 18:08:44 +0800 - rev 421450
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1388152 - Save abbreviated state name of address-level1 select element rather than its value in form autofill submission. r=lchang, r=MattN, a=lizzard MozReview-Commit-ID: IjZKzEdLlq5
2c15a6ed11f7: Bug 1390816 - Part 2: Add browser test for sync enabled case. r=lchang, a=lizzard
steveck-chung <schung@mozilla.com> - Thu, 17 Aug 2017 12:18:24 +0800 - rev 421449
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1390816 - Part 2: Add browser test for sync enabled case. r=lchang, a=lizzard MozReview-Commit-ID: FpsaoaMc6U4
cb236dfdd7bb: Bug 1340425 - Add back the magic GC in DoShutdown() to avoid intermittent leaks. r=smaug, a=lizzard
Andrew McCreight <continuation@gmail.com> - Wed, 23 Aug 2017 10:27:12 -0700 - rev 421448
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1340425 - Add back the magic GC in DoShutdown() to avoid intermittent leaks. r=smaug, a=lizzard MozReview-Commit-ID: CNkjPk9FLKj
fe5af9d9fdb2: Bug 1387918 - Retrieve current array for owner in aria owns hash table. r=surkov, a=jcristau
Eitan Isaacson <eitan@monotonous.org> - Mon, 28 Aug 2017 09:32:26 -0400 - rev 421447
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1387918 - Retrieve current array for owner in aria owns hash table. r=surkov, a=jcristau
67363a144710: Bug 1387377 - Don't run gtest or awsy on devedition builds. r=jmaher, a=test-only
Rob Wood <rwood@mozilla.com> - Thu, 24 Aug 2017 12:49:28 -0400 - rev 421446
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1387377 - Don't run gtest or awsy on devedition builds. r=jmaher, a=test-only MozReview-Commit-ID: 2siiOBftTYs
fe81d9af21d6: Bug 1335236 - Fix intermittent test_TelemetrySend.js due to flaky time tests. r=chutten, a=test-only
Alessio Placitelli <alessio.placitelli@gmail.com> - Mon, 28 Aug 2017 18:38:59 +0200 - rev 421445
Push 7686 by ryanvm@gmail.com at 2017-08-28 18:25 +0000
Bug 1335236 - Fix intermittent test_TelemetrySend.js due to flaky time tests. r=chutten, a=test-only On very fast builds (OPT, PGO) this test can fail intermittently because the time it takes to send a ping and receive a reply is 0. Account for that by replacing all the "greater than" checks with "greater or equal than". MozReview-Commit-ID: JvEo2rCbJj6
53dc3cc7dba6: no bug - Bumping Fennec l10n changesets r=release a=l10n-bump
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Mon, 28 Aug 2017 08:00:19 -0700 - rev 421444
Push 7685 by ffxbld at 2017-08-28 15:00 +0000
no bug - Bumping Fennec l10n changesets r=release a=l10n-bump br -> 0c692a161e6a es-AR -> 63e6fd7fd0d7 fa -> d352c27cb418 fi -> 0cea56079961 hu -> 4eef43d685ea nl -> 5676db0716a9 rm -> 6b8e6367d9d0 sk -> 8434673d6af8 tr -> 62966e6ad370
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip