5131400190142ce57036f9e1d50db2324d981ac8: Bug 1408044 - stop using about.dtd as an example in firefox-ui/puppeteer/marionette docs/tests, r=whimboo
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Tue, 14 Nov 2017 23:37:04 +0000 - rev 392258
Push 55516 by gijskruitbosch@gmail.com at Fri, 17 Nov 2017 00:00:55 +0000
Bug 1408044 - stop using about.dtd as an example in firefox-ui/puppeteer/marionette docs/tests, r=whimboo MozReview-Commit-ID: 4zog9pSgCs9
249a8177ad915734b83c357d49213e26d889b377: Bug 1417264 - Write .mozconfig.json from Python; r=nalexander
Gregory Szorc <gps@mozilla.com> - Mon, 13 Nov 2017 17:45:03 -0800 - rev 392257
Push 55515 by gszorc@mozilla.com at Thu, 16 Nov 2017 23:59:24 +0000
Bug 1417264 - Write .mozconfig.json from Python; r=nalexander In order to determine if we need to re-run configure, we write a JSON file representing the evaluated mozconfig. If this JSON file changes, configure (and config.status for that matter) is out of data and it is re-executed. This commit moves the generation of that JSON file to Python. MozReview-Commit-ID: 636rpSY7gOm
41492b2ba4e147fb22de42989582978d9e624729: Bug 1417264 - Write objdir .mozconfig from Python; r=nalexander
Gregory Szorc <gps@mozilla.com> - Mon, 13 Nov 2017 17:31:14 -0800 - rev 392256
Push 55515 by gszorc@mozilla.com at Thu, 16 Nov 2017 23:59:24 +0000
Bug 1417264 - Write objdir .mozconfig from Python; r=nalexander This is a pretty straightforward port of the logic. But we even go a step further: we delete the file in the objdir if there is no source mozconfig! MozReview-Commit-ID: AHFFzy6mXRY
523f39e23b7f90c8e91bdc0c275324ac85e21c0a: Bug 1417264 - Remove target for autoconf.mk; r=nalexander
Gregory Szorc <gps@mozilla.com> - Mon, 13 Nov 2017 17:22:38 -0800 - rev 392255
Push 55515 by gszorc@mozilla.com at Thu, 16 Nov 2017 23:59:24 +0000
Bug 1417264 - Remove target for autoconf.mk; r=nalexander This target isn't referenced elsewhere in client.mk. It appears to be dead. When this target became orphaned, I don't know. I suspect at some point some included .mk file attempted to "include autoconf.mk." But I'm not sure what file that would have been or when it would have changed. FWIW, autoconf.mk is generated by config.status, courtesy of it being listed in CONFIGURE_SUBST_FILES. MozReview-Commit-ID: AcPrihAou11
308804a30cd321d2066b83151981db93afea33aa: Bug 1417264 - Write .mozconfig.mk file from Python; r=nalexander
Gregory Szorc <gps@mozilla.com> - Mon, 13 Nov 2017 16:22:42 -0800 - rev 392254
Push 55515 by gszorc@mozilla.com at Thu, 16 Nov 2017 23:59:24 +0000
Bug 1417264 - Write .mozconfig.mk file from Python; r=nalexander The file is a filtered version of the make file that we previously started generating for client.mk. Why there is special casing for UPLOAD_EXTRA_FILES, I'm not sure. This smells fishy and is something I'd like to take a look at once all code is ported out of client.mk. The removal of the logic from client.mk meant that we could remove a bunch of code from client.mk related to loading mozconfig files. We can now simply include the auto-generated make file directly and be done with it. MozReview-Commit-ID: 4M5NElQA7iR
7e4030a95e89972ecb0d02ed5fa168ff0ea8d300: Bug 1417264 - Move printing of mozconfig lines to Python; r=nalexander
Gregory Szorc <gps@mozilla.com> - Mon, 13 Nov 2017 15:35:16 -0800 - rev 392253
Push 55515 by gszorc@mozilla.com at Thu, 16 Nov 2017 23:59:24 +0000
Bug 1417264 - Move printing of mozconfig lines to Python; r=nalexander We write the file that client.mk is printing from Python. We can also log it from there pretty easily. So do that. MozReview-Commit-ID: 7eeugdOJR5b
5ca22a0120c4f3a03886eabce033799f3943ca00: Bug 1417264 - Refactor code for writing mozconfig make file; r=nalexander
Gregory Szorc <gps@mozilla.com> - Mon, 13 Nov 2017 16:14:47 -0800 - rev 392252
Push 55515 by gszorc@mozilla.com at Thu, 16 Nov 2017 23:59:24 +0000
Bug 1417264 - Refactor code for writing mozconfig make file; r=nalexander Upcoming commits need to move more logic from client.mk. It will be easier if we have a list of lines in the mozconfig as a local variable. MozReview-Commit-ID: 1wFZTfWLGP9
dcd749d0982c546897661a7acbbf534a0499c5ef: Bug 1415878 - Accept both Chrome arrays and CSS colors for all properties. r=jaws
Tim Nguyen <ntim.bugs@gmail.com> - Thu, 16 Nov 2017 12:40:53 +0000 - rev 392251
Push 55514 by ntim.bugs@gmail.com at Thu, 16 Nov 2017 23:57:09 +0000
Bug 1415878 - Accept both Chrome arrays and CSS colors for all properties. r=jaws MozReview-Commit-ID: 6NkIUZKWkBI
02a5419402370bda38a58ee0a271c414081c9e7e: Bug 1389149 - Conditionally create the compositor hit-test info items. r=mstange
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 15 Nov 2017 11:39:45 -0500 - rev 392250
Push 55513 by kgupta@mozilla.com at Thu, 16 Nov 2017 23:55:31 +0000
Bug 1389149 - Conditionally create the compositor hit-test info items. r=mstange Create hit-test info items (if enabled) for each frame that is not invisible to hit-testing. This is not optimized at all yet, so it creates a lot of display items if enabled. MozReview-Commit-ID: LFqoaZ9e99F
3b4cc859f55dda6518d71dd8c030f915d643a008: Bug 1389149 - Add a new display item to carry the compositor hit-test info to WR. r=mstange
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 15 Nov 2017 11:39:45 -0500 - rev 392249
Push 55513 by kgupta@mozilla.com at Thu, 16 Nov 2017 23:55:31 +0000
Bug 1389149 - Add a new display item to carry the compositor hit-test info to WR. r=mstange This also adds a flag to the nsDisplayListBuilder to better control the creation of these items. MozReview-Commit-ID: BbeRGDjd2ie
45332b138026fc08b3a7923c4bc91a8313ec6a3e: Bug 1389149 - Add WR bindings for setting hit-test info and doing hit-tests. r=mstange
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 15 Nov 2017 11:39:44 -0500 - rev 392248
Push 55513 by kgupta@mozilla.com at Thu, 16 Nov 2017 23:55:31 +0000
Bug 1389149 - Add WR bindings for setting hit-test info and doing hit-tests. r=mstange This exposes some functions on wr::DisplayListBuilder to set hit-test info and to do hit-tests. The mechanism to set hit-test info is made a little more generic than is actually used in this patchset, because doing it this way allows for more optimization possibilities. Specifically, the API allows setting some hit-testing state which is then applied to all display items that are created until that state is updated or cleared. An alternative would be to specify the hit-testing state explicitly when creating particular display items; however doing that would force the call sites that create the display items to compute or obtain the hit-testing state, which would make the code less encapsulated and harder to refactor/optimize. MozReview-Commit-ID: EJoCFv83iu8
1bfcc78675d00fece2cb38f8799226aff5743d2a: Bug 1389149 - Extract the logic from nsDisplayLayerEventRegions::AddFrame into a more reusable form. r=mstange
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 15 Nov 2017 11:39:44 -0500 - rev 392247
Push 55513 by kgupta@mozilla.com at Thu, 16 Nov 2017 23:55:31 +0000
Bug 1389149 - Extract the logic from nsDisplayLayerEventRegions::AddFrame into a more reusable form. r=mstange This introduces a enum bitset type that encapsulates some of the interesting properties that frames have that make it interesting for hit-testing in the compositor. This type is designed so it can be sent directly to webrender and gotten back in the hit-test. MozReview-Commit-ID: GCxV7ZaoJd1
3ae93d5fd98cf913839e16d77d10f7b9f4717ad5: Bug 1414167 - Add offer/answer labels to local and remote sdp headings on about:webrtc. r=drno,smaug
Michael Froman <mfroman@mozilla.com> - Wed, 15 Nov 2017 13:40:09 -0600 - rev 392246
Push 55512 by mfroman@nostrum.com at Thu, 16 Nov 2017 23:53:16 +0000
Bug 1414167 - Add offer/answer labels to local and remote sdp headings on about:webrtc. r=drno,smaug Add a new |offerer| field to RTCStatsReport. Based on offerer, label the local sdp as offer or answer. Based on offerer, label the remote sdp as offer or answer. MozReview-Commit-ID: 4jdWP8tpr9w
25f0af5e17cf9d84171072154c296cfacb7fb7a5: Bug 1417035 - Stop using <plaintext> in JSON Viewer r=Honza
Oriol Brufau <oriol-bugzilla@hotmail.com> - Tue, 14 Nov 2017 01:34:21 +0100 - rev 392245
Push 55511 by ryanvm@gmail.com at Thu, 16 Nov 2017 23:51:25 +0000
Bug 1417035 - Stop using <plaintext> in JSON Viewer r=Honza MozReview-Commit-ID: ADGZiyMTaAL
0c859e8212004f19a46e0d80abb83368699c23c4: Bug 1416368 - Remove unreferenced "statusbarpanel-text" class;r=dao
Brian Grinstead <bgrinstead@mozilla.com> - Fri, 10 Nov 2017 14:53:40 -0800 - rev 392244
Push 55510 by bgrinstead@mozilla.com at Thu, 16 Nov 2017 23:50:29 +0000
Bug 1416368 - Remove unreferenced "statusbarpanel-text" class;r=dao MozReview-Commit-ID: DsNpoB81O40
2e0ea0c63d14269f1840955cc5f3c27bc32384da: Bug 1416368 - Remove unused statusbarpanel-* bindings;r=dao
Brian Grinstead <bgrinstead@mozilla.com> - Fri, 10 Nov 2017 14:48:34 -0800 - rev 392243
Push 55510 by bgrinstead@mozilla.com at Thu, 16 Nov 2017 23:50:29 +0000
Bug 1416368 - Remove unused statusbarpanel-* bindings;r=dao MozReview-Commit-ID: I6QKxP6joag
c946d67c779ac6045b7523fde7422760bb83a2e5: Bug 1411739 Use window::IsSecureContext to determine if screensharing is allowed instead of checking for https r=jib
Tom Ritter <tom@mozilla.com> - Thu, 26 Oct 2017 11:09:29 -0500 - rev 392242
Push 55509 by ryanvm@gmail.com at Thu, 16 Nov 2017 23:48:37 +0000
Bug 1411739 Use window::IsSecureContext to determine if screensharing is allowed instead of checking for https r=jib MozReview-Commit-ID: HCKY1bNcpy4
ba04b951526312d17eb9f7891f0d87ce3f84de6f: servo: Merge #19236 - Update WR (hit test fix, render target pool optimizations, picture tree) (from glennw:update-wr-pic); r=jdm
Glenn Watson <github@intuitionlibrary.com> - Thu, 16 Nov 2017 15:11:10 -0600 - rev 392241
Push 55508 by servo-vcs-sync@mozilla.com at Thu, 16 Nov 2017 23:46:39 +0000
servo: Merge #19236 - Update WR (hit test fix, render target pool optimizations, picture tree) (from glennw:update-wr-pic); r=jdm Source-Repo: https://github.com/servo/servo Source-Revision: fa61bfb83a7d7d9160e0384bb651e9b019c206ce
d2baa4bea136555ac96bd5aa7207e93452cec697: servo: Merge #19235 - style: Add infra to differentiate chrome and UA sheets (from emilio:chrome-props); r=xidorn
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 16 Nov 2017 14:01:39 -0600 - rev 392240
Push 55508 by servo-vcs-sync@mozilla.com at Thu, 16 Nov 2017 23:46:39 +0000
servo: Merge #19235 - style: Add infra to differentiate chrome and UA sheets (from emilio:chrome-props); r=xidorn This keeps the behavior of stuff being accessible from chrome stylesheets being the same of content sheets except on the UA origin. That will be changed in a followup. Source-Repo: https://github.com/servo/servo Source-Revision: e07245cabacdb0cfb597bfc3864abea6d567a1c6
e43433d076326b04ac16fa40b14c3650ffe56687: servo: Merge #18984 - Initial steps of Mutation testing (from dsandeephegde:master); r=jdm
Sandeep Hegde <dsandeephegde@gmail.com> - Thu, 16 Nov 2017 11:51:01 -0600 - rev 392239
Push 55508 by servo-vcs-sync@mozilla.com at Thu, 16 Nov 2017 23:46:39 +0000
servo: Merge #18984 - Initial steps of Mutation testing (from dsandeephegde:master); r=jdm <!-- Please describe your changes on the following line: --> - Added one strategy of mutation which is replacing occurrences && to ||. - Added test mapping framework for running mutation tests corresponding to a mutant. - Added one test_mapping.json to map source file in a folder to WPT test. - Added README mentioning about Mutation testing. - Added CI script to invoke mutation test. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes #18529 (github issue number if applicable). - [x] These changes do not require tests because it is a python script to run mutation test and does not change any behavior. <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> Source-Repo: https://github.com/servo/servo Source-Revision: 50f11e3584c9c0255098bdd438b11a84c093b197
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip