4a274293090db1dce0d2bbce05ebb6f4cf7f45ec: Backed out changeset fd642e0cca77 (bug 1316330) for causing bug 1332433
Iris Hsiao <ihsiao@mozilla.com> - Fri, 20 Jan 2017 14:30:20 +0800 - rev 353690
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Backed out changeset fd642e0cca77 (bug 1316330) for causing bug 1332433
cd4fc47221cb3c5333f0b23fcb1dac38c8c2b35d: Bug 1331873 - Null-check tab in TelemetryReportingPolicyImpl._openFirstRunPage's progress listener since it can be called synchronously before we have a reference to the tab. r=Gijs, a=jcristau
Dão Gottwald <dao@mozilla.com> - Wed, 18 Jan 2017 11:11:05 +0100 - rev 353689
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1331873 - Null-check tab in TelemetryReportingPolicyImpl._openFirstRunPage's progress listener since it can be called synchronously before we have a reference to the tab. r=Gijs, a=jcristau MozReview-Commit-ID: Gcktb3x7o4W
5a6e8c89b306ba8f959822c38f0b0ca3664e8b53: Bug 1330018 - Ensure we always unwrap CpowEntries. r=bholley, r=billm, a=jcristau
Andrew McCreight <continuation@gmail.com> - Fri, 13 Jan 2017 13:50:35 -0800 - rev 353688
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1330018 - Ensure we always unwrap CpowEntries. r=bholley, r=billm, a=jcristau We can drop async messages that contain CPOWs, which can cause us to leak them either until we successfully send a CPOW or forever, depending on the direction of the message. This is causing intermittent leaks until shutdown with e10s-multi. MozReview-Commit-ID: 3iIaIBZKZR2
338a1630d1db0573f0ac96be426f5b6f5198d474: Bug 1331808 - IconRequest.moveToNextIcon(): Throw exception if removing current item failed. r=Grisha, a=lizzard
Sebastian Kaspari <s.kaspari@gmail.com> - Wed, 18 Jan 2017 15:06:44 +0100 - rev 353687
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1331808 - IconRequest.moveToNextIcon(): Throw exception if removing current item failed. r=Grisha, a=lizzard MozReview-Commit-ID: 2dfgG7N9bX6
eb526a55f19acc56a92148607dd6cd74f526592c: Bug 1331808 - IconDescriptorComparator: Return consistent order for compared items. r=Grisha, a=lizzard
Sebastian Kaspari <s.kaspari@gmail.com> - Wed, 18 Jan 2017 14:50:35 +0100 - rev 353686
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1331808 - IconDescriptorComparator: Return consistent order for compared items. r=Grisha, a=lizzard Previously if we could not compare two icon descriptions we'd always return the "right" one. This does not create a consistent order if the parameters are flipped. As a result some operations on a TreeSet can fail (like remove()). MozReview-Commit-ID: EYPlhzGUEnD
84e2bee07c24e8d76b0093df609bc30f67b3d55e: Bug 1331849 - Replace NS_NewNativeLocalFile with NS_NewLocalFile in dom. r=smaug, a=jcristau
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 18 Jan 2017 14:58:37 +0100 - rev 353685
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1331849 - Replace NS_NewNativeLocalFile with NS_NewLocalFile in dom. r=smaug, a=jcristau
313fd5d293cdf66a4dfd6a76a2ac7e77506d8e2a: Bug 1325259 - Fix A8_RowProc_Opaque to not use legacy broken lerp. r=vliu, a=jcristau
Lee Salzman <lsalzman@mozilla.com> - Wed, 18 Jan 2017 10:15:09 -0500 - rev 353684
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1325259 - Fix A8_RowProc_Opaque to not use legacy broken lerp. r=vliu, a=jcristau MozReview-Commit-ID: FU7WxzQ3n7T
9bb207f947d83100c0f5bcd2b6baecc6ec24d431: Bug 1330998 - Invalidate pluginreg.dat based on whether the flash-only pref is flipped, so that if users switch between 52 and 52ESR it gets updated correctly. r=qdot, a=jcristau
Benjamin Smedberg <benjamin@smedbergs.us> - Tue, 17 Jan 2017 13:44:13 -0500 - rev 353683
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1330998 - Invalidate pluginreg.dat based on whether the flash-only pref is flipped, so that if users switch between 52 and 52ESR it gets updated correctly. r=qdot, a=jcristau MozReview-Commit-ID: 64yamsyIudD
38d2a128e0a96f24a7c02a636318f2c7387de960: Bug 1322337 - Load color bitmaps in SkFontHost_cairo when building with FreeType before 2.5.0. r=mchang, a=jcristau
Lee Salzman <lsalzman@mozilla.com> - Tue, 17 Jan 2017 12:27:16 -0500 - rev 353682
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1322337 - Load color bitmaps in SkFontHost_cairo when building with FreeType before 2.5.0. r=mchang, a=jcristau MozReview-Commit-ID: Ay7hJi7RK4T
584b0b8506252b3bf0863cf2c87ee71e5e998c00: Bug 1331510 - Remove unused shared/widgets.css stylesheet from inspector.xhtml. r=pbro, a=jcristau
Julian Descottes <jdescottes@mozilla.com> - Tue, 17 Jan 2017 01:16:44 +0100 - rev 353681
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1331510 - Remove unused shared/widgets.css stylesheet from inspector.xhtml. r=pbro, a=jcristau MozReview-Commit-ID: KQhgnxnkv2B
811c33f3350790b66f9803de91107823bf30756f: Bug 1328966 - Accept \r as a valid line ending. r=alwu, a=sledru
Ralph Giles <giles@mozilla.com> - Thu, 12 Jan 2017 11:20:26 -0800 - rev 353680
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1328966 - Accept \r as a valid line ending. r=alwu, a=sledru See https://w3c.github.io/webvtt/#webvtt-line-terminator for allowed values. MozReview-Commit-ID: C62Lu4PNQRE
d73abe84cc5132e5f9d06204505fb1c6055c2051: Bug 1319764 - Ensure Gtk window unmap workaround is actually used. r=karlt, a=jcristau
Jamie Nicol <jnicol@mozilla.com> - Fri, 13 Jan 2017 14:23:29 +0000 - rev 353679
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1319764 - Ensure Gtk window unmap workaround is actually used. r=karlt, a=jcristau We were miscounting the number of manual configure events which we needed to send gtk as the workaround for bug 1225044, causing it not to work in some cases. This is because configure events can come from more sources than were counting. Decrement mPendingConfigures only as far as zero, like configure_request_count in gtk_window_configure_event(). MozReview-Commit-ID: GxpR2Zozxor
64c904cb97764d74dfc4c2ad805cb7fc9155b3a3: Bug 1316514 - If we attempt to make the 'Highlight All' toggle a global setting, then we need to set the pref when toggled. r=Gijs, a=jcristau
Mike de Boer <mdeboer@mozilla.com> - Fri, 13 Jan 2017 17:27:18 +0100 - rev 353678
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1316514 - If we attempt to make the 'Highlight All' toggle a global setting, then we need to set the pref when toggled. r=Gijs, a=jcristau What you see first is the removal of the line `this._highlightAll = aHighlight;`, which is repeated in the `_setHighlightAll` method. This line was put here initially to make the test_findbar_events.xul test pass but in fact makes it so that the pref is never set in `_setHighlightAll`! In other words, we never actually persisted the 'Highlight All' state properly. Reading further: the `_dispatchFindEvent` attaches some findbar state flags to the event details, including the value of `_highlightAll`. Even though none of our consumers use it currently (haven't checked if TB does, though), you can cancel further execution of highlighting all ranges. Since the `_setHighlightAll` doesn't do that kind of processing, but merely makes sure the internal state is up to snuff, is persisted properly and the buttons are updated, I moved it up to be invoked before dispatching the event. MozReview-Commit-ID: 4BBy4FR1r5c
832fbf29c8a4aa40a4c7c3be8fa687c7e8763be5: Bug 1329631 - Only automatically open login manager autocomplete upon first marking. r=daleharvey, a=jcristau
Matthew Noorenberghe <mozilla@noorenberghe.ca> - Thu, 12 Jan 2017 14:26:29 -0500 - rev 353677
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1329631 - Only automatically open login manager autocomplete upon first marking. r=daleharvey, a=jcristau MozReview-Commit-ID: EnKmOSjs6G4
877cfd319e73a837731275d3cd4675bc27f9b0d8: Bug 1328038 - Refuse to play High 4:4:4 Predictive Profile. r=JamesCheng, a=jcristau
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 03 Jan 2017 06:58:09 +1100 - rev 353676
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1328038 - Refuse to play High 4:4:4 Predictive Profile. r=JamesCheng, a=jcristau It is not supported by Windows WMF. MozReview-Commit-ID: 2OyjC0qGwD4
f273dcc18ec664cb58443c4d3bb02fd147aa4c6c: Bug 1327210 - Make sure we can flip remoteness on a customizemode tab if the user somehow finds a way of navigating away. r=dao, a=jcristau
Mike Conley <mconley@mozilla.com> - Tue, 10 Jan 2017 13:56:15 -0500 - rev 353675
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1327210 - Make sure we can flip remoteness on a customizemode tab if the user somehow finds a way of navigating away. r=dao, a=jcristau A check for the customizemode attribute was added to SessionStore.restoreTabContent back when we removed the about:customizing preloading hackery in bug 1014185. This was added to prevent the extra work of unnecessarily restoring the content for a tab that was in customize mode (since the content is actually hidden). However, there are ways for a user to attempt to browse away from customize mode in the current tab - for example, going to their Home page with Alt-Home. When we do this in e10s mode, we do a "remoteness flip" to make the hidden about:blank browser be remote, which causes us to go through the SessionStore machinery to do the session swap to the new remote browser. The problem is when we hit the restoreTabContent part - we hit the condition where the customizemode attribute is set to true, and then we bail out, which means we never finish the swap. We're, at this point, in a half-restored state that never resolves. This patch makes it so that in restoreTabContent, if loadArguments is not null (so we've been given arguments on where to send the browser _next_ on top of its newly restored history), we don't skip just because the customizemode attribute is set. MozReview-Commit-ID: HwW7y2EKJvn
998f11970867282c85b89385a08bc172ce5b02d2: Bug 1320991 - Support --with-system-{nss,nspr} in modules/libmar. r=glandium, a=jcristau
Mike Shal <mshal@mozilla.com> - Tue, 20 Dec 2016 16:37:18 -0500 - rev 353674
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1320991 - Support --with-system-{nss,nspr} in modules/libmar. r=glandium, a=jcristau The problem with the modules/libmar/tests/moz.build file when building --with-system-nspr and --with-system-nss is that the nss libraries don't exist in the tree, so they fail when trying to copy into the test directory. However, it turns out that the libraries copied into the test directory aren't even used when building with an in-tree copy, because the xpcshell launcher sets LD_LIBRARY_PATH to point to dist/bin. Since we use the dist/bin copies anyway for an in-tree build, we can stop copying them into the test directory and simultaneously fix the --with-system build. The DEFINES can also go away since this directory doesn't actually build anything. MozReview-Commit-ID: Bk2f28wc9ZJ
e6d6e457c4f7aaae803a880b26bd0949fbc9fee2: Bug 1298676 - Part 3: Disable I/O interposition when manually taking crashdumps. r=ted, a=jcristau
Nathan Froyd <froydnj@mozilla.com> - Tue, 10 Jan 2017 16:31:25 -0500 - rev 353673
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1298676 - Part 3: Disable I/O interposition when manually taking crashdumps. r=ted, a=jcristau
74b93a29d034530c5de1dd6336a30e151f7949f9: Bug 1298676 - Part 2: Add an AutoIOInterposerDisable RAII class. r=aklotz, a=jcristau
Nathan Froyd <froydnj@mozilla.com> - Tue, 10 Jan 2017 16:31:25 -0500 - rev 353672
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1298676 - Part 2: Add an AutoIOInterposerDisable RAII class. r=aklotz, a=jcristau This will ensure the I/O Interposer is re-enabled after temporarily disabling it.
742559e3393fb7dd29e2a1072a583fbaace1c2c7: Bug 1298676 - Part 1: Add IOInterposer::Enable(). r=aklotz, a=jcristau
Nathan Froyd <froydnj@mozilla.com> - Tue, 10 Jan 2017 16:31:25 -0500 - rev 353671
Push 6795 by jlund@mozilla.com at Mon, 23 Jan 2017 14:19:46 +0000
Bug 1298676 - Part 1: Add IOInterposer::Enable(). r=aklotz, a=jcristau In some parts of the crash reporter, we need to disable I/O interposition, then turn it back on. We didn't have a function for re-enabling the I/O interposer...until now.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 tip