387015ba9c7462a3aa639f7de3c6c17be48bdb08: Bug 1317359 - Move add_old_configure_* functions to util.configure. r=chmanchester
Mike Hommey <mh+mozilla@glandium.org> - Tue, 15 Nov 2016 14:35:22 +0900 - rev 439678
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1317359 - Move add_old_configure_* functions to util.configure. r=chmanchester
0c8359a83645538a6eb7ff7cc935a9115426e8ec: Bug 1317593 - Fix logic in settings vcs_share_base r=gps
Rail Aliiev <rail@mozilla.com> - Tue, 15 Nov 2016 06:17:51 +0100 - rev 439677
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1317593 - Fix logic in settings vcs_share_base r=gps MozReview-Commit-ID: 7GVvOjNESqZ
d09e8a3b7875af81f391fe46ae6da3febbb37363: bug 1315668 construct menuitem style contexts from paths r=stransky+263117
Karl Tomlinson <karlt+@karlt.net> - Tue, 15 Nov 2016 17:11:14 +1300 - rev 439676
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
bug 1315668 construct menuitem style contexts from paths r=stransky+263117 instead of using the context belonging to a widget. Only the style context is cached, instead of the whole widget. Using the style context from a widget meant that rendering displayed the initial appearance of animations after state changes, but there was no invalidation to trigger the final rendering in the animations. Style contexts constructed from paths do not incorporate animations. (See gtk_css_path_node_update_style() in GTK.) Therefore they provide the appropriate rendering for Gecko's model, which is not expecting animations. There is no mechanism available to display animations when using style contexts constructed from paths, but the GtkWidget animation design is also not suitable for rendering potentially multiple elements each in a different state of their animation. This contexts-from-paths approach can be extended also to other widget types, but this is a smaller change intended for uplift to other branches to address a regression in menuitem rendering. MozReview-Commit-ID: EFV7swWQtm4
1693f10ca33e6f46f5b0b20b7b0f3ac5171be0f7: bug 1315668 CreateStyleForWidget: store classes on context instead of path r=stransky+263117
Karl Tomlinson <karlt+@karlt.net> - Tue, 15 Nov 2016 15:29:06 +1300 - rev 439675
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
bug 1315668 CreateStyleForWidget: store classes on context instead of path r=stransky+263117 CreateStyleForWidget() then provides the same behavior with g_style_context_save() as contexts from widget root style nodes. MozReview-Commit-ID: 6lRCp3XOoRr
749bc3f069a8a20954221ed32c9aea4d57062e35: bug 1315668 use style context instead of widget for menuitem dimensions r=stransky+263117
Karl Tomlinson <karlt+@karlt.net> - Tue, 15 Nov 2016 16:11:38 +1300 - rev 439674
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
bug 1315668 use style context instead of widget for menuitem dimensions r=stransky+263117 This is necessary to switch from caching GtkWidgets to caching GtkStyleContexts only. MozReview-Commit-ID: 6Rwinr4AY8l
e0ca38de294a2d8e60cdb819ca0fdfe10d16ab15: bug 1315668 remove use of gtk_container_get_border_width from menuitems r=stransky+263117
Karl Tomlinson <karlt+@karlt.net> - Mon, 14 Nov 2016 16:13:50 +1300 - rev 439673
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
bug 1315668 remove use of gtk_container_get_border_width from menuitems r=stransky+263117 The GtkContainer border-width property defaults to zero. It is not influenced by theme CSS. While theme engines can theoretically modify default values for properties of any class, I don't think that is something that needs to be supported. Removing this code is necessary to switch from caching GtkWidgets to caching GtkStyleContexts only. MozReview-Commit-ID: IxgM8qjfK3a
1927e94b7a173a8a702ceaea5fe026e221e90cd5: Bug 1303679 - Remove Places roots, reading list items, and pinned sites from the Sync server. r=markh
Kit Cambridge <kit@yakshaving.ninja> - Wed, 09 Nov 2016 14:23:54 -0800 - rev 439672
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1303679 - Remove Places roots, reading list items, and pinned sites from the Sync server. r=markh MozReview-Commit-ID: AhOBOnXsTYi
3b851a13d9292d06db747072cf14978b01d036d5: Bug 1308084 - Silence noisy warning in nsChannelClassifier::ShouldEnableTrackingProtection(). r=gcp
Francois Marier <francois@mozilla.com> - Thu, 10 Nov 2016 21:01:00 -0800 - rev 439671
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1308084 - Silence noisy warning in nsChannelClassifier::ShouldEnableTrackingProtection(). r=gcp MozReview-Commit-ID: 68n7476sVUM
6d4c987877fa4136b4f5e35ca525155e5124c505: Bug 1317090: Remove js::FindBody; r=arai
Benjamin Bouvier <benj@benj.me> - Tue, 15 Nov 2016 19:45:37 +0100 - rev 439670
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1317090: Remove js::FindBody; r=arai MozReview-Commit-ID: EmR0HZEYvW7
b660931ce41d684d37848ff6646129b0fe99e3f1: Bug 1316446 - Improve mach taskcluster-load-image r=gps
Jonas Finnemann Jensen <jopsen@gmail.com> - Thu, 10 Nov 2016 18:05:52 -0800 - rev 439669
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1316446 - Improve mach taskcluster-load-image r=gps MozReview-Commit-ID: 3Y8fI5WXP1Y
5d62e2bc7b593ed79ef048618350aaed7ab0a94a: Bug 1307871 - Add new console frontend support for 'Enable timestamps' pref. r=bgrins
Tim Nguyen <ntim.bugs@gmail.com> - Tue, 15 Nov 2016 19:23:47 +0000 - rev 439668
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1307871 - Add new console frontend support for 'Enable timestamps' pref. r=bgrins MozReview-Commit-ID: FshE769sETL
2be680105fcd756c8789cc38571ad00d4dd20a97: Backed out 3 changesets (bug 1271765) for win8 mochitest(5) failures a=backout
Wes Kocher <wkocher@mozilla.com> - Tue, 15 Nov 2016 10:50:59 -0800 - rev 439667
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Backed out 3 changesets (bug 1271765) for win8 mochitest(5) failures a=backout Backed out changeset 022a4a018996 (bug 1271765) Backed out changeset 1d96f03289f8 (bug 1271765) Backed out changeset 57317a080c99 (bug 1271765)
429e0bd037aaaad037d9d8315bca0f04fae11928: Bug 1317330 - Increase Mn verbosity for all mozharness initiated runs; r=whimboo
Andreas Tolfsen <ato@mozilla.com> - Mon, 14 Nov 2016 16:10:58 +0000 - rev 439666
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1317330 - Increase Mn verbosity for all mozharness initiated runs; r=whimboo Following bug 1311116 which reduces the Marionette log verbosity for local builds, this increases it on on all try jobs through passing the `-vv` (very verbose, equating to `Log.Level.Trace`) flag to the Marionette test harness. MozReview-Commit-ID: ELGgJph6QZo
c3b28797c209b71e2e966dc41bd0c228ba3196df: Bug 1275943 - Ensure job tasks are added to target set even if no try syntax specified, r=dustin
Andrew Halberstadt <ahalberstadt@mozilla.com> - Mon, 14 Nov 2016 14:29:50 -0500 - rev 439665
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1275943 - Ensure job tasks are added to target set even if no try syntax specified, r=dustin Job tasks are tasks that are not tied to a specific build or test. As such, they cannot be scheduled with the regular -p/-u try syntax options. There exists a -j try syntax option, to schedule them, which defaults to running "all" of them if not specified. However, there is a bug here where they will only default to "all" if a try syntax exists in the commit message. They will not be considered if a developer pushes to try without a try syntax. This happens because self.jobs is initially initialized with '[]' and we use None to determine when to schedule "all" later on. I want to move towards a world without try syntax, so we should start improving the UX of the no try syntax use case. Note: When I say "schedule" here, I mean added to the target set. They may still be optimized away. MozReview-Commit-ID: 4TrC84RGiaL
7d6d40b8751d9cb1cb950fe9a7fe130a46f66f6c: Bug 1313787 - Find relevant dlls on Windows when packaging an artifact build. r=glandium
Chris Manchester <cmanchester@mozilla.com> - Fri, 11 Nov 2016 00:20:17 -0800 - rev 439664
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1313787 - Find relevant dlls on Windows when packaging an artifact build. r=glandium MozReview-Commit-ID: KJq8ouh6Umi
ee65eebbbef90bb6a73b7be5ebadac176d875e88: Bug 1305421 - Implement chrome.identity, r=kmag
Shane Caraveo <scaraveo@mozilla.com> - Mon, 14 Nov 2016 13:02:02 -0800 - rev 439663
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1305421 - Implement chrome.identity, r=kmag MozReview-Commit-ID: LCAbodtV4XZ
1fe99466c9f9baac154feca8acfef89c14af0848: Bug 1316828 - Allow finer control over narration speed, r=eeejay
Timothy Guan-tin Chien <timdream@gmail.com> - Fri, 11 Nov 2016 18:51:04 +0800 - rev 439662
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1316828 - Allow finer control over narration speed, r=eeejay This patch updates the available speed for user from 8 different speeds to 40. MozReview-Commit-ID: DZXIhqQERIv
4fc83233df681d000842ef2945bc6207d519efd2: Bug 1317473 - Make GMPService accept paths with mixed dir separators. r=jesup
Chris Pearce <cpearce@mozilla.com> - Tue, 15 Nov 2016 10:56:43 +1300 - rev 439661
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1317473 - Make GMPService accept paths with mixed dir separators. r=jesup The mochitest harness on Windows sets MOZ_GMP_PATH to paths with a mixture of Windows and UNIX dir separators, and the NS_NewLocalFile() call in GMPServiceParent::AddOnGMPThread() fails on this input. We've had this problem before, and if we fixed the test harness to give us input with platform specific line endings somebody would likely just break this again someday and have this issue again, so just make the GMP service normalize the paths it's given to have consistent dir separators. This makes test_peerConnection_basicH264Video.html pass when run locally on my Windows machine. MozReview-Commit-ID: 88hSvTdZuWg
b7ccea321333c5b935bc04fe2455d2c522b4da9d: Bug 1317180, part 8 - Remove unused optional argument chmodallowed to _canonicalType. r=billm
Andrew McCreight <continuation@gmail.com> - Mon, 14 Nov 2016 11:18:00 -0800 - rev 439660
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1317180, part 8 - Remove unused optional argument chmodallowed to _canonicalType. r=billm As of the previous patch, this argument no longer does anything.
0dea817804ac71d9e8720b3dc0d36d47189aaf71: Bug 1317180, part 7 - Remove TypeSpec fields myChmod and otherChmod that are never set. r=billm
Andrew McCreight <continuation@gmail.com> - Mon, 14 Nov 2016 11:17:12 -0800 - rev 439659
Push 36064 by rthijssen@mozilla.com at Wed, 16 Nov 2016 13:38:27 +0000
Bug 1317180, part 7 - Remove TypeSpec fields myChmod and otherChmod that are never set. r=billm The other fields, spec, array, and nullable, are set in some places. Also remove a dead chunk of code with a FIXME that refers to a bug that was WONTFIXed in 2010.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip