b21cadc4d1bfe6e8e4863033eae6b60a5d9af479: Bug 1329068 - Fix layout issue for PropertiesView r?ntim,honza draft
Ricky Chien <rchien@mozilla.com> - Sun, 15 Jan 2017 14:30:18 +0800 - rev 462347
Push 41706 by bmo:rchien@mozilla.com at Tue, 17 Jan 2017 03:39:05 +0000
Bug 1329068 - Fix layout issue for PropertiesView r?ntim,honza MozReview-Commit-ID: HKW38QrPovm
aa6d586314be0c2ab6f14e4eeb4761bbd7449f45: Bug 1325812 - If the url has scheme but not http or https, treat as query. r?seabstian draft
Nevin Chen <cnevinchen@gmail.com> - Mon, 16 Jan 2017 18:19:27 +0800 - rev 462346
Push 41705 by bmo:cnevinchen@gmail.com at Tue, 17 Jan 2017 03:19:53 +0000
Bug 1325812 - If the url has scheme but not http or https, treat as query. r?seabstian MozReview-Commit-ID: 9hTtlTSejCu
4a60414d27788efd7083d0c4063e0c6e15d35606: Bug 1320744 - Part 2, implement nsIThreadRetargetableRequest in HttpChannelChild. r=mayhemer draft
Shih-Chiang Chien <schien@mozilla.com> - Thu, 29 Dec 2016 14:10:54 +0800 - rev 462345
Push 41704 by schien@mozilla.com at Tue, 17 Jan 2017 03:04:56 +0000
Bug 1320744 - Part 2, implement nsIThreadRetargetableRequest in HttpChannelChild. r=mayhemer MozReview-Commit-ID: FyLXlkQde3h
9a4928756ceb9c47b64753963c50f091263f88d3: Bug 1320744 - Part 1, make refcounter of HttpChannelChild thread-safe. r=mayhemer draft
Shih-Chiang Chien <schien@mozilla.com> - Tue, 17 Jan 2017 10:54:25 +0800 - rev 462344
Push 41704 by schien@mozilla.com at Tue, 17 Jan 2017 03:04:56 +0000
Bug 1320744 - Part 1, make refcounter of HttpChannelChild thread-safe. r=mayhemer MozReview-Commit-ID: 5Br1WLlpvcR
349b0260c8d872480518ee7f8317f2b649d1166d: Bug 1328824 - Test if about:blocked can be loaded in a secure context. draft
Henry <hchang@mozilla.com> - Fri, 13 Jan 2017 00:08:45 +0800 - rev 462343
Push 41703 by hchang@mozilla.com at Tue, 17 Jan 2017 02:58:59 +0000
Bug 1328824 - Test if about:blocked can be loaded in a secure context. MozReview-Commit-ID: GQAfd4xuRJT
ad74584c52f92c97ff4bbb4808051be7034aaa4b: Bug 1330858 - display cookie object value at same row draft
Fred Lin <gasolin@mozilla.com> - Tue, 17 Jan 2017 10:39:15 +0800 - rev 462342
Push 41702 by bmo:gasolin@mozilla.com at Tue, 17 Jan 2017 02:41:24 +0000
Bug 1330858 - display cookie object value at same row MozReview-Commit-ID: FysBslkAoaZ
f81835544ab8e371a6d59a609a88567fce2183f5: Backed out changeset 5d72e00c604a (bug 1326067) for near-permaorange in wasm-06.js in Windows cgc builds
Phil Ringnalda <philringnalda@gmail.com> - Mon, 16 Jan 2017 18:30:03 -0800 - rev 462341
Push 41702 by bmo:gasolin@mozilla.com at Tue, 17 Jan 2017 02:41:24 +0000
Backed out changeset 5d72e00c604a (bug 1326067) for near-permaorange in wasm-06.js in Windows cgc builds
f10afdb666c50436c20e666eb7aabca63b2f01a7: Bug 1327294. When drawing XUL images allow some decoding if it's fast. r=aosmond
Timothy Nikkel <tnikkel@gmail.com> - Mon, 16 Jan 2017 14:12:51 -0600 - rev 462340
Push 41702 by bmo:gasolin@mozilla.com at Tue, 17 Jan 2017 02:41:24 +0000
Bug 1327294. When drawing XUL images allow some decoding if it's fast. r=aosmond We aren't likely to implement predictive size decoding for XUL images. So instead do some sync decoding when we Draw them at their specified size. This will avoid a paint where we don't draw the image, or draw it at the wrong size, followed later by the correctly sized image.
2b43e179370261a0a71b59ba6ebb24260ecba0a1: Bug 1322085 - Make devtools/server/actors/*.js eslint-clean. r=ntim
Dalimil Hajek <dalimilhajek@gmail.com> - Mon, 16 Jan 2017 12:51:00 -0500 - rev 462339
Push 41702 by bmo:gasolin@mozilla.com at Tue, 17 Jan 2017 02:41:24 +0000
Bug 1322085 - Make devtools/server/actors/*.js eslint-clean. r=ntim
685121de3c2c10ecce02029c0feb18ed94b1242e: Bug 1328354 - Update old-configure.in to require libpng 1.6.28. r=jrmuizel
Glenn Randers-Pehrson <glennrp+bmo@gmail.com> - Fri, 06 Jan 2017 15:24:00 -0500 - rev 462338
Push 41702 by bmo:gasolin@mozilla.com at Tue, 17 Jan 2017 02:41:24 +0000
Bug 1328354 - Update old-configure.in to require libpng 1.6.28. r=jrmuizel
7b2836951988cbc233747e63092e6e331c18d958: Bug 1328354 - Update in-tree libpng to version 1.6.28. r=jrmuizel
Glenn Randers-Pehrson <glennrp+bmo@gmail.com> - Sat, 07 Jan 2017 09:32:00 -0500 - rev 462337
Push 41702 by bmo:gasolin@mozilla.com at Tue, 17 Jan 2017 02:41:24 +0000
Bug 1328354 - Update in-tree libpng to version 1.6.28. r=jrmuizel
16e87b06a1d0673cef4845e3de711cbb3d483842: Merge m-c to m-i
Phil Ringnalda <philringnalda@gmail.com> - Mon, 16 Jan 2017 14:50:05 -0800 - rev 462336
Push 41702 by bmo:gasolin@mozilla.com at Tue, 17 Jan 2017 02:41:24 +0000
Merge m-c to m-i
2b34eb5807f33f01faea45ace0b5cba977008a39: bug 1330730 - make sure mAccessibles and mChildDocs are cleared by DocAccessibleparent::Destroy() r=davidb
Trevor Saunders <tbsaunde@tbsaunde.org> - Fri, 13 Jan 2017 14:50:29 -0500 - rev 462335
Push 41702 by bmo:gasolin@mozilla.com at Tue, 17 Jan 2017 02:41:24 +0000
bug 1330730 - make sure mAccessibles and mChildDocs are cleared by DocAccessibleparent::Destroy() r=davidb This shouldn't be necessary because shutting down all the proxies and child documents should already do it, but we might as well be sure.
362ba8c68a290ee2cde1afea82c66effd9cac3ce: bug 1330730 - ignore events delivered to a destroyed DocAccessibleParent r=smaug
Trevor Saunders <tbsaunde@tbsaunde.org> - Fri, 13 Jan 2017 14:25:15 -0500 - rev 462334
Push 41702 by bmo:gasolin@mozilla.com at Tue, 17 Jan 2017 02:41:24 +0000
bug 1330730 - ignore events delivered to a destroyed DocAccessibleParent r=smaug After bug 1329814 a DocAccessibleParent can be shutdown by the parent process before a content process has started shutting down the document that DocAccessibleParent represents. That means the content processcan send an event from a live document to a DocAccessibleParent that has already been destroyed.
f4966566dfcf5d9b68e7c54e57fed6b543a6362e: Bug 1330793 - Refactor int32 index guard to not modify the input register. r=evilpie
Jan de Mooij <jdemooij@mozilla.com> - Mon, 16 Jan 2017 22:53:09 +0100 - rev 462333
Push 41702 by bmo:gasolin@mozilla.com at Tue, 17 Jan 2017 02:41:24 +0000
Bug 1330793 - Refactor int32 index guard to not modify the input register. r=evilpie
ba03fe14feef1b7315a2670ccdcf1760165c63df: Bug 1291821 - Post: remove unused files r=rnewman draft
Grisha Kruglov <gkruglov@mozilla.com> - Tue, 29 Nov 2016 13:36:26 -0800 - rev 462332
Push 41701 by gkruglov@mozilla.com at Tue, 17 Jan 2017 02:37:52 +0000
Bug 1291821 - Post: remove unused files r=rnewman MozReview-Commit-ID: 4qM5vx4AQyQ
12f47b3d739596295aa2d01e1f88159716e42eb6: Bug 1291821 - Allow BatchingDownloader to resume downloads using offset r=rnewman draft
Grisha Kruglov <gkruglov@mozilla.com> - Mon, 16 Jan 2017 18:15:13 -0800 - rev 462331
Push 41701 by gkruglov@mozilla.com at Tue, 17 Jan 2017 02:37:52 +0000
Bug 1291821 - Allow BatchingDownloader to resume downloads using offset r=rnewman BatchingDownloader uses provided RepositoryStateProvider instance in order to track offset and high water mark as it performs batching. The state holder objects are initialized by individual ServerSyncStages, and prefixes are used to ensure keys won't clash. Two RepositoryStateProvider implementations are used: persistent and non-persistent. Non-persistent state provider does not allow for resuming after a sync restart, while persistent one does. Persistent state provider is used by the history stage. It is fetched oldest-first, and records are applied to live storage as they're downloaded. These conditions let use resume downloads. It's also possible to resume downloads for stages which use a persistent buffer, but currently we do not have any. Offset value and its context is reset if we hit a 412 error; it is maintained if we hit a sync deadline, allowing us to minimize number of records we'll redownload. BatchingDownloaderController owns resuming and context checking logic. High water mark (h.w.m.) is maintained across syncs and used instead of stage's "last-synced" timestamp if said stage is set to fetch oldest-first and explicitely allows use of a h.w.m. Server15RepositorySession provides correct timestamp to RecordsChannel, decoupling BatchingDownloader from this logic. MozReview-Commit-ID: IH28YrDU4vW
6437c5a09476675003739aae54db4560052b87a1: Bug 1317363 Implement the new sideloading flow r?florian draft
Andrew Swan <aswan@mozilla.com> - Mon, 16 Jan 2017 18:24:14 -0800 - rev 462330
Push 41700 by aswan@mozilla.com at Tue, 17 Jan 2017 02:34:24 +0000
Bug 1317363 Implement the new sideloading flow r?florian MozReview-Commit-ID: JgloWKYAhlK
b9e569a5f7d09f7a70705d73a8ad0a37220c29e8: Bug 1291821 - Post: remove unused files r=rnewman draft
Grisha Kruglov <gkruglov@mozilla.com> - Tue, 29 Nov 2016 13:36:26 -0800 - rev 462329
Push 41699 by gkruglov@mozilla.com at Tue, 17 Jan 2017 02:23:34 +0000
Bug 1291821 - Post: remove unused files r=rnewman MozReview-Commit-ID: 4qM5vx4AQyQ
aa0d5c952f350ce0d4c93d1fa87da0b323ac064f: Bug 1291821 - Allow BatchingDownloader to resume downloads using offset r=rnewman draft
Grisha Kruglov <gkruglov@mozilla.com> - Mon, 16 Jan 2017 18:15:13 -0800 - rev 462328
Push 41699 by gkruglov@mozilla.com at Tue, 17 Jan 2017 02:23:34 +0000
Bug 1291821 - Allow BatchingDownloader to resume downloads using offset r=rnewman BatchingDownloader uses provided RepositoryStateProvider instance in order to track offset and high water mark as it performs batching. The state holder objects are initialized by individual ServerSyncStages, and prefixes are used to ensure keys won't clash. Two RepositoryStateProvider implementations are used: persistent and non-persistent. Non-persistent state provider does not allow for resuming after a sync restart, while persistent one does. Persistent state provider is used by the history stage. It is fetched oldest-first, and records are applied to live storage as they're downloaded. These conditions let use resume downloads. It's also possible to resume downloads for stages which use a persistent buffer, but currently we do not have any. Offset value and its context is reset if we hit a 412 error; it is maintained if we hit a sync deadline, allowing us to minimize number of records we'll redownload. BatchingDownloaderController owns resuming and context checking logic. High water mark (h.w.m.) is maintained across syncs and used instead of stage's "last-synced" timestamp if said stage is set to fetch oldest-first and explicitely allows use of a h.w.m. MozReview-Commit-ID: IH28YrDU4vW
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip