53ac5a12a19b1243e8df3b68de2183a0d853eec0: Bug 1285541 - touch clobber to fix bustage
Carsten "Tomcat" Book <cbook@mozilla.com> - Fri, 08 Jul 2016 16:32:49 +0200 - rev 304216
Push 79270 by cbook@mozilla.com at Fri, 08 Jul 2016 14:33:06 +0000
Bug 1285541 - touch clobber to fix bustage
aea13acdf417e8178e731645bc1701163d191ee5: Bug 1285541 - Update cubeb to revision b8aebef3. r=padenot
Paul Adenot <paul@paul.cx> - Fri, 08 Jul 2016 15:56:56 +0200 - rev 304215
Push 79269 by paul@paul.cx at Fri, 08 Jul 2016 13:57:04 +0000
Bug 1285541 - Update cubeb to revision b8aebef3. r=padenot Patches by achronop. MozReview-Commit-ID: 2RurT5Y3CHo
04ee49f5bd4a16e88eefcb1ca8e890274d25593d: Bug 1271751 - part 8 - fix bug in nsTArray_CopyWithConstructors; r=erahm
Nathan Froyd <froydnj@gmail.com> - Fri, 08 Jul 2016 16:59:04 -0400 - rev 304214
Push 79268 by nfroyd@mozilla.com at Fri, 08 Jul 2016 13:00:46 +0000
Bug 1271751 - part 8 - fix bug in nsTArray_CopyWithConstructors; r=erahm The backwards copying case in MoveOverlappingRegion had a bug: rather than destroying each element from the source range as we moved it, we would always destroy the element at the beginning of the source range. Fortunately, none of the existing types that were copied via constructors seem to trigger the problematic code.
acf15b7ae545af2f723a7a15b6a7cde8fa9cf63b: Bug 1271751 - part 7 - remove nsTArray_CopyWith*::Copy*; r=erahm
Nathan Froyd <froydnj@gmail.com> - Fri, 08 Jul 2016 16:59:05 -0400 - rev 304213
Push 79268 by nfroyd@mozilla.com at Fri, 08 Jul 2016 13:00:46 +0000
Bug 1271751 - part 7 - remove nsTArray_CopyWith*::Copy*; r=erahm After all the previous patches, we never call these functions. Any copying required by nsTArray is taken care of by other means.
a4ec59ebd89761e0c4f5e84082740fc28537182c: Bug 1271751 - part 6 - make ShiftData actually move its elements rather than copying; r=erahm
Nathan Froyd <froydnj@gmail.com> - Fri, 08 Jul 2016 16:59:05 -0400 - rev 304212
Push 79268 by nfroyd@mozilla.com at Fri, 08 Jul 2016 13:00:46 +0000
Bug 1271751 - part 6 - make ShiftData actually move its elements rather than copying; r=erahm This change eliminates the last use of the Copy* family of functions.
862be98e16060a61fb36485e5a1243973b1a0dd2: Bug 1271751 - part 5 - use MoveNonOverlappingRegion instead of CopyNonOverlappingRegion; r=erahm
Nathan Froyd <froydnj@gmail.com> - Fri, 08 Jul 2016 16:59:05 -0400 - rev 304211
Push 79268 by nfroyd@mozilla.com at Fri, 08 Jul 2016 13:00:46 +0000
Bug 1271751 - part 5 - use MoveNonOverlappingRegion instead of CopyNonOverlappingRegion; r=erahm In all of the calls to CopyNonOverlappingRegion from within nsTArray, we don't care about the contents of the source afterwards. So we can use moves instead of copies to potentially make things more efficient.
a458e6f337ce9ebbd2c96508d8c05e3a78a14ff7: Bug 1271751 - part 4 - rename CopyNonOverlappingRegionWithHeader to MoveNonOverlappingRegionWithHeader; r=erahm
Nathan Froyd <froydnj@gmail.com> - Fri, 08 Jul 2016 16:59:05 -0400 - rev 304210
Push 79268 by nfroyd@mozilla.com at Fri, 08 Jul 2016 13:00:46 +0000
Bug 1271751 - part 4 - rename CopyNonOverlappingRegionWithHeader to MoveNonOverlappingRegionWithHeader; r=erahm Whenever we're copying the header, we can be guaranteed that we're never going to use the elements from the old array afterward, so can move (in the C++ sense) the elements rather than copying them.
c726b0821954d4df564983e0fd59c97ef1c271d6: Bug 1271751 - part 3 - add Move{Non,}OverlappingRegion; r=erahm
Nathan Froyd <froydnj@gmail.com> - Fri, 08 Jul 2016 16:59:05 -0400 - rev 304209
Push 79268 by nfroyd@mozilla.com at Fri, 08 Jul 2016 13:00:46 +0000
Bug 1271751 - part 3 - add Move{Non,}OverlappingRegion; r=erahm We'll need these for future patches as we transition nsTArray to use moves for most of its operations rather than copies. The implementation of these functions are essentially cut-and-paste versions of the Copy* functions, but using moves.
7247f68ba1108f4d9447536060e0c27463ff78ff: Bug 1271751 - part 2 - rename {Copy,Move}Elements to something more accurate; r=erahm
Nathan Froyd <froydnj@gmail.com> - Fri, 08 Jul 2016 16:59:05 -0400 - rev 304208
Push 79268 by nfroyd@mozilla.com at Fri, 08 Jul 2016 13:00:46 +0000
Bug 1271751 - part 2 - rename {Copy,Move}Elements to something more accurate; r=erahm The names {Copy,Move}Elements are based on the use of mem{cpy,move}, respectively. However, I submit that we really want the names to reflect the C++ operations being done, rather than the underlying implementation details. So let's rename these to reflect that we are always copying the elements, and discriminate between the two cases based on whether the regions being copied overlap or not. Bring CopyHeaderAndElements along for the ride, as well.
910cbc036dce871cea5fffa307fc7a5d9def55f1: Bug 1271751 - part 1 - provide out-of-class definitions for some nsTArray functions; r=erahm
Nathan Froyd <froydnj@gmail.com> - Fri, 08 Jul 2016 16:59:05 -0400 - rev 304207
Push 79268 by nfroyd@mozilla.com at Fri, 08 Jul 2016 13:00:46 +0000
Bug 1271751 - part 1 - provide out-of-class definitions for some nsTArray functions; r=erahm This change enables some of the methods in nsTArray to be lazily instantiated, particularly the ones that care about whether the element type is copyable. Since we have a number of places where nsTArray is used with move-only types, we need to ensure that unless methods requiring copyability are actually called, those methods are not instantiated.
55e0ce158c0bdf1fe52fffb0420bbef9b5f6f2d5: Bug 1271751 - part 0 - remove heap functions from nsTArray; r=erahm
Nathan Froyd <froydnj@gmail.com> - Fri, 08 Jul 2016 16:59:05 -0400 - rev 304206
Push 79268 by nfroyd@mozilla.com at Fri, 08 Jul 2016 13:00:46 +0000
Bug 1271751 - part 0 - remove heap functions from nsTArray; r=erahm They are unused, except for tests.
e0e56c2e18810c5aa29b8c11b7c491e9721e4ce0: Bug 1283438 - Set AUTOCLOBBER to empty for l10n r=glandium.
Justin Wood <Callek@gmail.com> - Thu, 30 Jun 2016 15:25:55 -0400 - rev 304205
Push 79267 by Callek@gmail.com at Fri, 08 Jul 2016 11:46:29 +0000
Bug 1283438 - Set AUTOCLOBBER to empty for l10n r=glandium. Needed because buildbot clones/checks out from the repo head (of default) and then updates to the rev for the nightly we're pulling, which can cause CLOBBER file changes to initiate an unwanted clobber of the object directory where we just pulled the nightly binary from. Even when CLOBBER hasn't actually been touched in the changeset range we're looking at between nightlies. MozReview-Commit-ID: 154d2iZeHgd
86d2baff7ec89962f3da863cc2a82e0b078a815d: Merge mozilla-central to mozilla-inbound
Carsten "Tomcat" Book <cbook@mozilla.com> - Fri, 08 Jul 2016 12:16:57 +0200 - rev 304204
Push 79266 by cbook@mozilla.com at Fri, 08 Jul 2016 10:17:09 +0000
Merge mozilla-central to mozilla-inbound
45682df2d2d45e5a8385fd842579e661a4b60bc5: merge mozilla-inbound to mozilla-central a=merge
Carsten "Tomcat" Book <cbook@mozilla.com> - Fri, 08 Jul 2016 11:58:46 +0200 - rev 304203
Push 79266 by cbook@mozilla.com at Fri, 08 Jul 2016 10:17:09 +0000
merge mozilla-inbound to mozilla-central a=merge
401d1f8037f305ae0b9a09fd940343d87597a64a: merge fx-team to mozilla-central a=merge
Carsten "Tomcat" Book <cbook@mozilla.com> - Fri, 08 Jul 2016 11:57:15 +0200 - rev 304202
Push 79266 by cbook@mozilla.com at Fri, 08 Jul 2016 10:17:09 +0000
merge fx-team to mozilla-central a=merge
74dd49dcf6c944a1de2b1762ee328710aa4358a4: Bug 1285021 - Exclude urls starting with blob: from tab syncing. r=markh
Thom Chiovoloni <tchiovoloni@mozilla.com> - Thu, 07 Jul 2016 13:58:34 -0400 - rev 304201
Push 79266 by cbook@mozilla.com at Fri, 08 Jul 2016 10:17:09 +0000
Bug 1285021 - Exclude urls starting with blob: from tab syncing. r=markh MozReview-Commit-ID: 9ye7sO0tB5W
c4c4a4c442963a0151f43259763f64ace3c7acfb: Bug 1279443 - Don't capture session state during startup before we've restored history. r=sebastian
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 29 Jun 2016 18:24:13 +0200 - rev 304200
Push 79266 by cbook@mozilla.com at Fri, 08 Jul 2016 10:17:09 +0000
Bug 1279443 - Don't capture session state during startup before we've restored history. r=sebastian When restoring tabs on startup, the Java UI creates tab stubs for the tabs from the previous session. The selected foreground tab then starts loading as soon as Gecko is up and running. Meanwhile, the session store gets initialised, too and starts restoring history and other things for that tab. After history has been restored for an active tab, the session store reloads the current history entry, however by that time, depending on device speed, page size and how many other tabs the session store has to process during startup, the initial page load might have progressed far enough to have already triggered various events monitored by the session store, e.g. "pageshow". If those events arrive before tab restoring has finished, the session store will attempt to capture that tab's state, which will overwrite the values stored from the previous session. Once the page is then reloaded for restoring, wrong values (e.g. form data, scroll position, zoom level) might then be restored. Therefore, we now abort any attempts to capture a tab's state - for all tabs until the "sessionstore-windows-restored" notification has been received as a signal that the initial session restore during startup has finished - for the restored foreground tab until the location change notification is received after reloading MozReview-Commit-ID: HbhXcEUnRXQ
5fce05217908344626bbb231868be0d5f1dd4e78: Bug 1282830 - Trigger session saves when closing zombie tabs, too. r=sebastian
Jan Henning <jh+bugzilla@buttercookie.de> - Tue, 28 Jun 2016 23:29:57 +0200 - rev 304199
Push 79266 by cbook@mozilla.com at Fri, 08 Jul 2016 10:17:09 +0000
Bug 1282830 - Trigger session saves when closing zombie tabs, too. r=sebastian A tab being in a delay-loaded "zombie" state or not shouldn't have any influence on the behaviour of onTabRemove - since we remove it from the session store's sphere of influence, its __SS_data can be safely deleted anyway and whether or not a session save needs to be triggered should depend only on the aNoNotfication parameter passed by the caller. Otherwise, with the current behaviour, the fact that those tabs have been closed will not get saved to disk if no subsequent session save is triggered through any other means (e.g. selecting a different tab, scrolling, ...) before closing Firefox. MozReview-Commit-ID: IxjZRRutc7A
66a35bd16dbd48749a7f48654743bb8233142e62: Bug 1285253 - Change incorrect "text-anchor: left" to "start". r=jdescottes
Ian Moody <moz-ian@perix.co.uk> - Thu, 07 Jul 2016 13:48:16 +0100 - rev 304198
Push 79266 by cbook@mozilla.com at Fri, 08 Jul 2016 10:17:09 +0000
Bug 1285253 - Change incorrect "text-anchor: left" to "start". r=jdescottes Also fix a typo in a comment, "Rules" -> "Rulers" MozReview-Commit-ID: Gy5k3TR9JDM
16de376cf1eb7652afcd8d5a6552449eaffcf13e: Bug 1285418 - Update pdf.js to version 1.5.322. r=bdahl
Ryan VanderMeulen <ryanvm@gmail.com> - Thu, 07 Jul 2016 21:46:33 -0400 - rev 304197
Push 79266 by cbook@mozilla.com at Fri, 08 Jul 2016 10:17:09 +0000
Bug 1285418 - Update pdf.js to version 1.5.322. r=bdahl
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip