0dc7bfc7b0c1de8d390cea05f0248fbadeb4d5fc: Bug 1447879 - Cannot customize about:preferences#home content when sync or preference searching is disabled. r=k88hudson
Ed Lee <edilee@mozilla.com> - Wed, 30 May 2018 17:32:44 -0700 - rev 802527
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1447879 - Cannot customize about:preferences#home content when sync or preference searching is disabled. r=k88hudson Have the home preferences page notify when it loads instead of relying on findInPage to trigger sync pane to init. MozReview-Commit-ID: EJlJDfYBHFO
85c9f9c900314b7586d997bbedd67ccd8c8fad70: Bug 1464405 - Register FormAutofill resource URIs before checking if the feature should be enabled. r=MattN
Mike Conley <mconley@mozilla.com> - Mon, 28 May 2018 09:50:21 -0700 - rev 802526
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1464405 - Register FormAutofill resource URIs before checking if the feature should be enabled. r=MattN MozReview-Commit-ID: JU93hA0NBgL
4ae4cc41c1ad65a6a9735bff436ab97cc1dfa5ee: Bug 1465409 - Change lint rules for mediasource tests to prefer no spaces for array notation. r=jya
Bryce Van Dyk <bvandyk@mozilla.com> - Wed, 30 May 2018 08:18:54 -0400 - rev 802525
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1465409 - Change lint rules for mediasource tests to prefer no spaces for array notation. r=jya Change rules so we enforce ["foo", "bar"] rather than [ "foo", "bar" ]. MozReview-Commit-ID: KX6wJd8jmeJ
548c628a1059cf0c57fd73a3e4e141eed06bd685: Bug 1463751 - Tab-specific data not updated when tab is moved to another window and old window closes r=mixedpuppy
Oriol Brufau <oriol-bugzilla@hotmail.com> - Sat, 26 May 2018 21:57:58 +0200 - rev 802524
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1463751 - Tab-specific data not updated when tab is moved to another window and old window closes r=mixedpuppy MozReview-Commit-ID: IUC8OwV6YHY
930b30d0d0aab0905fabfb7cb61e39489dc5b1de: Bug 1388013 - Remove restriction of Python 2 in mozrunner; r=ahal
Dave Hunt <dhunt@mozilla.com> - Wed, 30 May 2018 13:21:51 +0100 - rev 802523
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1388013 - Remove restriction of Python 2 in mozrunner; r=ahal MozReview-Commit-ID: 1ARx4Jy2Z83
317c77708b22d7086f9171ac8893d371c43b79f9: Bug 1388013 - Support running |mach python-test| against Python 3 using pipenv; r=ahal
Dave Hunt <dhunt@mozilla.com> - Thu, 03 May 2018 10:34:22 +0100 - rev 802522
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1388013 - Support running |mach python-test| against Python 3 using pipenv; r=ahal This patch allows executing |mach python-test| against Python 3 by specifying the optional |--three| command line option. When this option is present, pipenv will be used to manage a virtual environment using Python 3 and attempt to run the tests. When it is not present, pipenv will not be used, and everything will work as it did before this patch. My original plan was to use pipenv regardless of the target version of Python, however I encountered several issues running some of the tests against our Python packages. Once all tests have been patched to run against Python 3, then we should be able to use pipenv when running them against Python 2. Note that this patch allows tests to run against Python 3, but there are plenty of issues preventing them from passing. With this patch in place we can start to add Python 3 support to our packages and have the tests running in CI to ensure we don't regress back to just supporting Python 2. MozReview-Commit-ID: BuU5gZK83hL IHG: changed taskcluster/ci/source-test/python.yml
eccc5f4ea53eef6622349846b92fac0d396372da: Bug 1388013 - Vendor jsmin via |mach vendor python|; r=ahal
Dave Hunt <dhunt@mozilla.com> - Wed, 30 May 2018 13:07:32 +0100 - rev 802521
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1388013 - Vendor jsmin via |mach vendor python|; r=ahal MozReview-Commit-ID: 197reaD9GdL
b2cbe24032838b09781adeee59427c561c60b367: Bug 1463087 - Instrument inspection of JS execution in the Web Console with event telemetry r=yulia
Michael Ratcliffe <mratcliffe@mozilla.com> - Thu, 24 May 2018 16:22:47 +0100 - rev 802520
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1463087 - Instrument inspection of JS execution in the Web Console with event telemetry r=yulia MozReview-Commit-ID: 2lri9Kzso7Q
375638c8a4332004266e23ef9c882d057d5d7d81: Bug 1463083 - Instrument inspection of inspector side panel switching with event telemetry r=yulia
Michael Ratcliffe <mratcliffe@mozilla.com> - Thu, 24 May 2018 14:21:49 +0100 - rev 802519
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1463083 - Instrument inspection of inspector side panel switching with event telemetry r=yulia MozReview-Commit-ID: ANPWNvYRfdH
c2139cedcc489d26e19a9858f9d30c8737c67778: Bug 1463081 - Instrument inspection of "Edit Rule" in Rule View with event telemetry r=yulia
Michael Ratcliffe <mratcliffe@mozilla.com> - Wed, 30 May 2018 17:53:29 +0100 - rev 802518
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1463081 - Instrument inspection of "Edit Rule" in Rule View with event telemetry r=yulia The changes to telemetry.js::recordEvent() were necessary because the optional value and extra params cannot be sent to Services.telemetry.recordEvent() as undefined without throwing... using null instead works just fine. MozReview-Commit-ID: CgoqSeR6mkl
edc3670ec282285c1757fabe1fb189f52c88dc76: Bug 1464496 - Part 2: Move the mRaw before the two booleans for better packing r=emilio
Nazım Can Altınova <canaltinova@gmail.com> - Thu, 31 May 2018 10:31:44 +0200 - rev 802517
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1464496 - Part 2: Move the mRaw before the two booleans for better packing r=emilio MozReview-Commit-ID: Gi4Is7RgVmN
d6e582ce9bab5ca688a024fb20eeba097ad45dfe: Bug 1464496 - Part 1: Merge ServoDeclarationBlock and DeclarationBlock r=emilio
Nazım Can Altınova <canaltinova@gmail.com> - Wed, 30 May 2018 18:15:25 +0200 - rev 802516
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1464496 - Part 1: Merge ServoDeclarationBlock and DeclarationBlock r=emilio MozReview-Commit-ID: By9fV70Oq0K
426ab5b84824dc046ad0796b0c4c836f33bd8bbc: Bug 1460907 - Implement AudioParamMap definitions. r=karlt,qdot
Arnaud Bienner <arnaud.bienner@gmail.com> - Sun, 13 May 2018 16:16:23 +0200 - rev 802515
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1460907 - Implement AudioParamMap definitions. r=karlt,qdot MozReview-Commit-ID: AdsI9QU3VOX
2f3835d852c0b273572543898b89b1ec53a0d6d0: Bug 1462390 - Extract history from JSTerm component; r=nchevobbe
Jan Odvarko <odvarko@gmail.com> - Thu, 31 May 2018 12:41:29 +0200 - rev 802514
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1462390 - Extract history from JSTerm component; r=nchevobbe MozReview-Commit-ID: DTlW1h2ACoI
437a8d7c128abf04b0a0d2d366cc5b58f292bc87: Merge mozilla-central to autoland. a=merge on a CLOSED TREE
Andreea Pavel <apavel@mozilla.com> - Thu, 31 May 2018 13:05:59 +0300 - rev 802513
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Merge mozilla-central to autoland. a=merge on a CLOSED TREE
646b7e8eb69b042e337ee97f3d1e7d3b40f2c2f5: Bug 1463580 - Autofill sometimes autocompletes in-the-middle (with >>) and doesn't autofill to the next slash. r=adw
Marco Bonardo <mbonardo@mozilla.com> - Tue, 29 May 2018 17:57:35 +0200 - rev 802512
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1463580 - Autofill sometimes autocompletes in-the-middle (with >>) and doesn't autofill to the next slash. r=adw MozReview-Commit-ID: J3rfTYDgpFN Also fixes Bug 1464328 - Autofill urls to-the-next-slash is broken.
ba9528133000abdb4cfd0d1fc7587ac63508520e: Backed out 3 changesets (bug 1388013) for build bustages e.g. ../python/mozbuild/mozpack/test/test_files.py on a CLOSED TREE
Andreea Pavel <apavel@mozilla.com> - Thu, 31 May 2018 11:48:19 +0300 - rev 802511
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Backed out 3 changesets (bug 1388013) for build bustages e.g. ../python/mozbuild/mozpack/test/test_files.py on a CLOSED TREE Backed out changeset eea857170a41 (bug 1388013) Backed out changeset c55bfefbd4e1 (bug 1388013) Backed out changeset 3a163da2b21b (bug 1388013)
4cab0dc8b7d9bec46ec24334a425e5d96a21002c: Bug 1444394 - Remove Element::UnsafeSetInnerHTML. r=bz,kmag
Johann Hofmann <jhofmann@mozilla.com> - Mon, 28 May 2018 22:55:52 +0200 - rev 802510
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1444394 - Remove Element::UnsafeSetInnerHTML. r=bz,kmag The last remaining user is already turned off and being removed in bug 1444395 so that we can finally remove this unsafe code and sleep a little better knowing that XSS through markup injections will be impossible in chrome contexts. MozReview-Commit-ID: KcZq8fRPiD4
eea857170a418231418d27bda675446e2d21b2b8: Bug 1388013 - Remove restriction of Python 2 in mozrunner; r=ahal
Dave Hunt <dhunt@mozilla.com> - Wed, 30 May 2018 13:21:51 +0100 - rev 802509
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1388013 - Remove restriction of Python 2 in mozrunner; r=ahal MozReview-Commit-ID: 1ARx4Jy2Z83
c55bfefbd4e1786bd90ed173bbef547dff8d84ef: Bug 1388013 - Support running |mach python-test| against Python 3 using pipenv; r=ahal
Dave Hunt <dhunt@mozilla.com> - Thu, 03 May 2018 10:34:22 +0100 - rev 802508
Push 111898 by gsquelart@mozilla.com at Thu, 31 May 2018 22:45:14 +0000
Bug 1388013 - Support running |mach python-test| against Python 3 using pipenv; r=ahal This patch allows executing |mach python-test| against Python 3 by specifying the optional |--three| command line option. When this option is present, pipenv will be used to manage a virtual environment using Python 3 and attempt to run the tests. When it is not present, pipenv will not be used, and everything will work as it did before this patch. My original plan was to use pipenv regardless of the target version of Python, however I encountered several issues running some of the tests against our Python packages. Once all tests have been patched to run against Python 3, then we should be able to use pipenv when running them against Python 2. Note that this patch allows tests to run against Python 3, but there are plenty of issues preventing them from passing. With this patch in place we can start to add Python 3 support to our packages and have the tests running in CI to ensure we don't regress back to just supporting Python 2. MozReview-Commit-ID: BuU5gZK83hL IHG: changed taskcluster/ci/source-test/python.yml
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip