9759594e223f25075dde334fe96af323bf33d144: Revert the newly-added tests from rev ff8566df88d5. a=test-only
Ryan VanderMeulen <ryanvm@gmail.com> - Thu, 02 Feb 2017 19:37:33 -0500 - rev 366863
Push 6873 by ryanvm@gmail.com at Fri, 03 Feb 2017 00:37:53 +0000
Revert the newly-added tests from rev ff8566df88d5. a=test-only
b9e7643b8be64976276573389670f70d57e1fe9f: Bug 1334537 - Make sure to clear out our external string cache if the length doesn't match, since our length no longer needs to match our stringbuffer. r=froydnj, a=lizzard
Boris Zbarsky <bzbarsky@mit.edu> - Wed, 01 Feb 2017 15:29:47 -0500 - rev 366862
Push 6872 by ryanvm@gmail.com at Fri, 03 Feb 2017 00:24:19 +0000
Bug 1334537 - Make sure to clear out our external string cache if the length doesn't match, since our length no longer needs to match our stringbuffer. r=froydnj, a=lizzard Without this change, we could do a "short" get of a string (e.g. from XMLHttpRequest), then do another get that returns the same stringbuffer but a longer length. But we wouldn't notice, hit our cache, and return the same, too-short, external string. The site would not see the new data it should have seen.
ff8566df88d5323305cc1592af072957e4ee1f34: Bug 1323324 tests. r=till, a=test-only
Boris Zbarsky <bzbarsky@mit.edu> - Mon, 19 Dec 2016 15:38:44 -0800 - rev 366861
Push 6872 by ryanvm@gmail.com at Fri, 03 Feb 2017 00:24:19 +0000
Bug 1323324 tests. r=till, a=test-only
757ad211356f4f91e4d8129c086e3018ecbd1460: Bug 1303298 - Use BrowserTestUtils.waitForErrorPage to wait for certerror page load. r=nhnt11, a=test-only
Johann Hofmann <jhofmann@mozilla.com> - Wed, 25 Jan 2017 16:19:04 +0100 - rev 366860
Push 6872 by ryanvm@gmail.com at Fri, 03 Feb 2017 00:24:19 +0000
Bug 1303298 - Use BrowserTestUtils.waitForErrorPage to wait for certerror page load. r=nhnt11, a=test-only MozReview-Commit-ID: BzT1cQAd9Qx
d3dcda2046c2b138522b4d07288ab4260a6f3e46: Bug 1335944 - Delay devicemanagerADB sdk check until connect() time. r=bc, a=test-only
Geoff Brown <gbrown@mozilla.com> - Thu, 02 Feb 2017 09:29:08 -0700 - rev 366859
Push 6872 by ryanvm@gmail.com at Fri, 03 Feb 2017 00:24:19 +0000
Bug 1335944 - Delay devicemanagerADB sdk check until connect() time. r=bc, a=test-only
3b07081139babab5746944d9e9356160f978ab4c: Bug 1120441 - Don't try to show tab-history panel if app has been shutdown. r=sebastian, a=jcristau
Andrzej Hunt <ahunt@mozilla.com> - Wed, 18 Jan 2017 22:09:20 +0100 - rev 366858
Push 6871 by ryanvm@gmail.com at Thu, 02 Feb 2017 19:05:34 +0000
Bug 1120441 - Don't try to show tab-history panel if app has been shutdown. r=sebastian, a=jcristau Showing the tab history panel involves a gecko call to retrieve tab history. This can be slow, meaning we have no idea what state the app will be in when the tab history data is returned. Thus we need to protect the code that shows the tab history fragment against a number of scenarios to avoid crashes in those cases where the app might be shutting down: 1. If onSaveInstanceState() has been called (which might happen before or after onPause(), and might be linked to app shutdown - but the docs don't appear to give any guarantees), fragment transactions cannot be performed. We protect against this by accepting loss of state in fragment transactions. 2. If the Activity has been completely destroyed, trying to perform a fragment transaction will likewise fail. We protect against this by not even trying to perform the transaction if we definitively know that the Activity is being shut down (ie isFinishing()). In both of these cases, we simply must accept that we're potentially losing UI state: i.e. a user could request the tab history panel via long-back-press, followed by exiting the app; we now end up never ever showing the panel. This scenario doesn't seem like a major loss - and fixing this issue properly would require significant investment (i.e. we would need to either cache tab history on frontend side, or cache the tab-history panel request - and it's not clear users will still care about seeing the panel the next time they open firefox). MozReview-Commit-ID: JsAK1By8yqn
1a6c3c479c469f83cfe12e0e12b6f9f296665b4f: Backed out changeset 790848ae6b7f (bug 1120441) for Android bustage.
Ryan VanderMeulen <ryanvm@gmail.com> - Thu, 02 Feb 2017 13:17:01 -0500 - rev 366857
Push 6870 by ryanvm@gmail.com at Thu, 02 Feb 2017 18:17:09 +0000
Backed out changeset 790848ae6b7f (bug 1120441) for Android bustage.
d171c36d484800b1bb00db1612460a7120dd2fdf: Bug 1322593 - Add test for multiple independent text changes under the same accessible. r=yzen, a=jcristau FIREFOX_52_0b3_BUILD1 FIREFOX_52_0b3_RELEASE
Trevor Saunders <tbsaunde@tbsaunde.org> - Fri, 20 Jan 2017 16:23:44 -0500 - rev 366856
Push 6869 by ryanvm@gmail.com at Thu, 02 Feb 2017 18:14:12 +0000
Bug 1322593 - Add test for multiple independent text changes under the same accessible. r=yzen, a=jcristau
5ec5c9a7719b756bf831b11c76c6467a2b0fd45e: Bug 1322593 - Test that unrelated text change events are not coalesced. r=yzen, a=jcristau
Trevor Saunders <tbsaunde@tbsaunde.org> - Thu, 19 Jan 2017 16:50:59 -0500 - rev 366855
Push 6869 by ryanvm@gmail.com at Thu, 02 Feb 2017 18:14:12 +0000
Bug 1322593 - Test that unrelated text change events are not coalesced. r=yzen, a=jcristau
d52e2bceab57d08544a310ef88ab4ca504238f72: Bug 1322593 - Allow asynchronous checking of text change events. r=yzen, a=jcristau
Trevor Saunders <tbsaunde@tbsaunde.org> - Thu, 19 Jan 2017 16:37:09 -0500 - rev 366854
Push 6869 by ryanvm@gmail.com at Thu, 02 Feb 2017 18:14:12 +0000
Bug 1322593 - Allow asynchronous checking of text change events. r=yzen, a=jcristau This allows us to check for multiple text change events that could come in any order.
61c451adc3b17e54853d4fe6a68045ed6e171414: Bug 1322593 - Don't coalesce non contiguous text changes under the same accessible. r=davidb, a=jcristau
Trevor Saunders <tbsaunde@tbsaunde.org> - Thu, 19 Jan 2017 16:35:17 -0500 - rev 366853
Push 6869 by ryanvm@gmail.com at Thu, 02 Feb 2017 18:14:12 +0000
Bug 1322593 - Don't coalesce non contiguous text changes under the same accessible. r=davidb, a=jcristau
8336a9d40a9a93ce81b4d47aff16c61c19bfe4c9: Bug 1322593 - Avoid merging text change events for unrelated accessibles. r=davidb, a=jcristau
Trevor Saunders <tbsaunde@tbsaunde.org> - Thu, 19 Jan 2017 15:13:54 -0500 - rev 366852
Push 6869 by ryanvm@gmail.com at Thu, 02 Feb 2017 18:14:12 +0000
Bug 1322593 - Avoid merging text change events for unrelated accessibles. r=davidb, a=jcristau
f72072777689bd6b37da3410699829090c146cb4: Bug 1322593 - Add match function for text change checker to stricten match based on modified text. r=tbsaunde, a=jcristau
Yura Zenevich <yzenevich@mozilla.com> - Thu, 19 Jan 2017 23:33:31 -0500 - rev 366851
Push 6869 by ryanvm@gmail.com at Thu, 02 Feb 2017 18:14:12 +0000
Bug 1322593 - Add match function for text change checker to stricten match based on modified text. r=tbsaunde, a=jcristau MozReview-Commit-ID: 44LEulhW671
1ad9c3c00e7d80da334596bfeb48641e7c118ad6: Bug 1307461 - Disable MediaPipelineTest.TestAudioSendNoMux. r=jesup, a=test-only
Dan Minor <dminor@mozilla.com> - Wed, 01 Feb 2017 12:07:25 -0500 - rev 366850
Push 6869 by ryanvm@gmail.com at Thu, 02 Feb 2017 18:14:12 +0000
Bug 1307461 - Disable MediaPipelineTest.TestAudioSendNoMux. r=jesup, a=test-only
f3bc1ad9fc3c91b5d1dd6e21daa080628250b1d9: Bug 1334538 - Do not update SHA1 bouncer aliases in Firefox 52. r=jlorenzo a=release DONTBUILD
Rail Aliiev <rail@mozilla.com> - Fri, 27 Jan 2017 13:17:23 -0500 - rev 366849
Push 6868 by raliiev@mozilla.com at Thu, 02 Feb 2017 16:08:49 +0000
Bug 1334538 - Do not update SHA1 bouncer aliases in Firefox 52. r=jlorenzo a=release DONTBUILD MozReview-Commit-ID: GcObzm1nzlP
4a6fa0969049899d50f0beea768bcd7c6a715b5b: Bug 1319531 - Ensure all streams provided by DatabaseFile can be read without generating NS_BASE_STREAM_WOULD_BLOCK errors. beta52 version. r=janv a=jcristau
Andrew Sutherland <asutherland@asutherland.org> - Mon, 30 Jan 2017 06:05:13 -0500 - rev 366848
Push 6867 by cbook@mozilla.com at Thu, 02 Feb 2017 16:06:21 +0000
Bug 1319531 - Ensure all streams provided by DatabaseFile can be read without generating NS_BASE_STREAM_WOULD_BLOCK errors. beta52 version. r=janv a=jcristau beta 52 patch changes: - minor bit-rot in context - test had to be devolved to use old-style generators and relevant idioms IndexedDB database operations are written such that they must execute synchronously. For this reason, the add/put operation reads/writes its Blobs to disk in a synchronous fashion. However, with the introduction of SendStream-backed Blobs for large (>1 MiB) blobs whose contents are streamed to the parent replacing nsStringInputStream-backed Blobs (whose contents were sent up in a single IPC message that might exceed the size limit and cause a crash), this has no longer been a safe assumption. However, the problems weren't immediately obvious because most pre-WASM Blobs are smaller than the 1MiB threshold and even when they exceeded the size, their memory-backed contents could rapidly be sent to the parent via IPC, making NS_BASE_STREAM_WOULD_BLOCK errors rare/hard to reproduce. (rr and its enforced single-threading is a good way to reproduce, however. Also, see the testing patch on the bug that introduces artificial delays into SendStream.) Included SpecialPowersObserver.jsm minor changes to "CreateFiles": - appendRelativePath is used instead of appendPath because appendPath only allows a single path component to be appended. In other words, file creation is limited to files at the root of the profile directory using appendPath, which is needlessly limiting. - outStream is now closed even if no data is provided. This is essential on windows where file deletion only occurs when all handles are closed. Without this fix, "RemoveFiles" side-effect of deleting the created files might not take effect until garbage collection runs and collects the outStream.
166a10fe355f19efa0d0009b7ccbced38ec24bb2: Bug 1334774 - re-introduce the hostname into ssl error messages, r=nhnt11 a=jcristau
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Sun, 29 Jan 2017 17:36:01 +0100 - rev 366847
Push 6866 by cbook@mozilla.com at Thu, 02 Feb 2017 16:03:26 +0000
Bug 1334774 - re-introduce the hostname into ssl error messages, r=nhnt11 a=jcristau MozReview-Commit-ID: CexcCq5qo1v
80636f3bf46c7cccacb0f3e4422a7344fa80b6e6: Bug 1334201 - Ignore window.opener for insecure form warnings. r=MattN a=jcristau
Johann Hofmann <jhofmann@mozilla.com> - Tue, 31 Jan 2017 10:34:06 +0100 - rev 366846
Push 6866 by cbook@mozilla.com at Thu, 02 Feb 2017 16:03:26 +0000
Bug 1334201 - Ignore window.opener for insecure form warnings. r=MattN a=jcristau MozReview-Commit-ID: BLuwIAWEYHi
87b018eade4650f4185910e364eeae7a9785649b: Bug 1329520 - Fix "memory/mozalloc/throw_gcc.h:35:1: note: declaration missing '[[noreturn]]' (libc++ 4.0)" r=nfroyd a=jcristau
Dimitry Andric <dimitry> - Fri, 27 Jan 2017 13:55:00 +0100 - rev 366845
Push 6866 by cbook@mozilla.com at Thu, 02 Feb 2017 16:03:26 +0000
Bug 1329520 - Fix "memory/mozalloc/throw_gcc.h:35:1: note: declaration missing '[[noreturn]]' (libc++ 4.0)" r=nfroyd a=jcristau
790848ae6b7fd673f9c8c3431b7011e01809eeb8: Bug 1120441 - Don't try to show tab-history panel if app has been shutdown. r=sebastian, a=ritu a=jcristau
Andrzej Hunt <ahunt@mozilla.com> - Wed, 18 Jan 2017 22:09:20 +0100 - rev 366844
Push 6866 by cbook@mozilla.com at Thu, 02 Feb 2017 16:03:26 +0000
Bug 1120441 - Don't try to show tab-history panel if app has been shutdown. r=sebastian, a=ritu a=jcristau Showing the tab history panel involves a gecko call to retrieve tab history. This can be slow, meaning we have no idea what state the app will be in when the tab history data is returned. Thus we need to protect the code that shows the tab history fragment against a number of scenarios to avoid crashes in those cases where the app might be shutting down: 1. If onSaveInstanceState() has been called (which might happen before or after onPause(), and might be linked to app shutdown - but the docs don't appear to give any guarantees), fragment transactions cannot be performed. We protect against this by accepting loss of state in fragment transactions. 2. If the Activity has been completely destroyed, trying to perform a fragment transaction will likewise fail. We protect against this by not even trying to perform the transaction if we definitively know that the Activity is being shut down (ie isFinishing()). In both of these cases, we simply must accept that we're potentially losing UI state: i.e. a user could request the tab history panel via long-back-press, followed by exiting the app; we now end up never ever showing the panel. This scenario doesn't seem like a major loss - and fixing this issue properly would require significant investment (i.e. we would need to either cache tab history on frontend side, or cache the tab-history panel request - and it's not clear users will still care about seeing the panel the next time they open firefox). MozReview-Commit-ID: JsAK1By8yqn
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip