9d7a310cb701aff7072c1ec8aae853fb125ce319: Bug 1243070 - Remove obsolete size-change code; r=snorp
Jim Chen <nchen@mozilla.com> - Mon, 01 Feb 2016 17:38:14 -0500 - rev 282634
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243070 - Remove obsolete size-change code; r=snorp Remove obsolete SIZE_CHANGED event and its handler in nsWindow. Also remove some other supporting code (such as gAndroidBounds and the FORCED_RESIZE event) that should be unnecessary by now.
9f0bf58364c731d8c6cec765703fddb9cadf674c: Bug 1243070 - Use native method to notify window size change; r=snorp
Jim Chen <nchen@mozilla.com> - Mon, 01 Feb 2016 17:38:14 -0500 - rev 282633
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243070 - Use native method to notify window size change; r=snorp Convert the SIZE_CHANGED event to a native method in GLController, and carry over the SIZE_CHANGED implementation to the new implementation in GLController. Some other changes were made for correctness in handling size changes.
a628353b83b83e812c660347af761c1ec10b8a88: Bug 1243069 - Control GeckoThread state entirely from C++ code; r=snorp
Jim Chen <nchen@mozilla.com> - Mon, 01 Feb 2016 17:38:14 -0500 - rev 282632
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243069 - Control GeckoThread state entirely from C++ code; r=snorp Right now, we rely on browser.js sending Gecko:Ready, to set the GeckoThread state to RUNNING upon receiving Gecko:Ready. This patch gets rid of this dependency on browser.js and Gecko:Ready.
24209390c44725189f73d4653317cf34400853e4: Bug 1243049 - Update robocop tests to use new prefs API; r=gbrown
Jim Chen <nchen@mozilla.com> - Mon, 01 Feb 2016 17:38:14 -0500 - rev 282631
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243049 - Update robocop tests to use new prefs API; r=gbrown Change old robocop prefs API to the new API and add helper classes for getting prefs. Also switch all tests that use prefs to use the new API.
c4b3686d3283f6e0b1e6540b320b40982232ee73: Bug 1243049 - Use PrefHelper.addObserver; r=snorp
Jim Chen <nchen@mozilla.com> - Mon, 01 Feb 2016 17:38:14 -0500 - rev 282630
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243049 - Use PrefHelper.addObserver; r=snorp Use the new PrefHelper.addObserver method for adding pref observers.
6244023e793b09c2367a3116dcccc16ffa077d15: Bug 1243049 - Convert browser.js prefs code to use observer; r=margaret
Jim Chen <nchen@mozilla.com> - Mon, 01 Feb 2016 17:38:14 -0500 - rev 282629
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243049 - Convert browser.js prefs code to use observer; r=margaret Convert the old prefs code in browser.js to use observer notifications that are sent by the new PrefsHelper implementation, in order to handle pseudo-prefs.
a9da983929fed0aba0d3b4c5f7f2740a21ea5289: Bug 1243049 - Implement new PrefsHelper native methods; r=snorp
Jim Chen <nchen@mozilla.com> - Mon, 01 Feb 2016 17:38:13 -0500 - rev 282628
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243049 - Implement new PrefsHelper native methods; r=snorp Implement the PrefsHelper native methods. The previous browser.js implementation supported "pseudo-prefs" that did not exist as actual prefs, but was accessible through PrefsHelper. In order to accommodate these pseudo-prefs, we send observer notifications in order to communicate with browser.js about prefs that we don't support.
c98df93878f204d8a22bbfd2210885f1b0b80c00: Bug 1243049 - Update native bindings for PrefsHelper; r=me
Jim Chen <nchen@mozilla.com> - Mon, 01 Feb 2016 17:38:13 -0500 - rev 282627
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243049 - Update native bindings for PrefsHelper; r=me Update auto-generated native bindings for PrefsHelper.
606bc36d35a1736f0313ee0bef8c392bfe5d4210: Bug 1243049 - Introduce new PrefsHelper implementation; r=snorp
Jim Chen <nchen@mozilla.com> - Mon, 01 Feb 2016 17:38:13 -0500 - rev 282626
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243049 - Introduce new PrefsHelper implementation; r=snorp Introduce a new implementation for PrefsHelper that does not use events or rely on browser.js for getting and/or setting prefs. Also add an addObserver method to better match the removeObserver method.
64ee9c353c06bced1deff104548bab5b9d0cd8c1: Bug 1164427 - Add w-p-t for elementFromPoint/elementsFromPoint on div with negative margins; r=roc
Kyle Machulis <kyle@nonpolynomial.com> - Thu, 28 Jan 2016 12:35:57 -0800 - rev 282625
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1164427 - Add w-p-t for elementFromPoint/elementsFromPoint on div with negative margins; r=roc
512497f6a7edcdbff533e4adc8f400de5b2845c0: Bug 1164427 - Implement elementsFromPoint; r=roc r=khuey
Kyle Machulis <kyle@nonpolynomial.com> - Sat, 16 Jan 2016 12:21:43 -0800 - rev 282624
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1164427 - Implement elementsFromPoint; r=roc r=khuey
c3dd7dab0b0018d1adc5ce6e3daf173ce812490b: Bug 1220502 - ignore not visible text nodes for tree update, r=tbsaunde, roc
Alexander Surkov <surkov.alexander@gmail.com> - Mon, 01 Feb 2016 17:05:45 -0500 - rev 282623
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1220502 - ignore not visible text nodes for tree update, r=tbsaunde, roc
53354197432f5f80d3bdcd7aaca801b09c85c239: Bug 1244166: Don't ignore stroke/fill properties in high-contrast mode, since doing so can produce icons that are invisible or whose colors are unrelated to the user's chosen high-contrast colors. r=longsonr
Daniel Holbert <dholbert@cs.stanford.edu> - Mon, 01 Feb 2016 11:23:09 -0800 - rev 282622
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1244166: Don't ignore stroke/fill properties in high-contrast mode, since doing so can produce icons that are invisible or whose colors are unrelated to the user's chosen high-contrast colors. r=longsonr
96c92e9d6216aa91e1eefa40c943c9ce5cf00adf: Bug 1243758 - Add --browser-chrome and --chunk-by-runtime flags to browser-chrome-coverage test. r=chmanchester
Joel Maher <jmaher@mozilla.com> - Wed, 27 Jan 2016 09:31:25 -0800 - rev 282621
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243758 - Add --browser-chrome and --chunk-by-runtime flags to browser-chrome-coverage test. r=chmanchester
1c6457541936f6df1ea797bfd545b906c738fcdf: Bug 1244720 - Modifications to tier 2 TaskCluster jobs. DONTBUILD. r=jmaher
Armen Zambrano Gasparnian <armenzg@mozilla.com> - Mon, 01 Feb 2016 16:11:12 -0500 - rev 282620
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1244720 - Modifications to tier 2 TaskCluster jobs. DONTBUILD. r=jmaher * add Jetpack definition * e10s mochitests were not using --e10s flag [1] * disable mochitest e10s since they're not green anymore * increase Marionette max runtime [1] Unfortunately, we had two payload entries defined for e10s mochitests. That would cause the first paylod (with --e10s) to be ignored.
b9dba72f9e97839358c225b4136218b53719c5fe: Bug 1243881 - patch 2 - unship performance.translateTime, r=bz
Andrea Marchesini <amarchesini@mozilla.com> - Mon, 01 Feb 2016 21:48:04 +0000 - rev 282619
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243881 - patch 2 - unship performance.translateTime, r=bz
52792f2aac93469dbc65af12be264570f04c6a1f: Bug 1243881 - patch 1 - unship performance.translateTime, r=bz
Andrea Marchesini <amarchesini@mozilla.com> - Mon, 01 Feb 2016 21:48:04 +0000 - rev 282618
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1243881 - patch 1 - unship performance.translateTime, r=bz
5f47728bef613bb0974c48028ac9af8d2f36a05c: Bug 1219094 - releng - kill api-11 mozconfigs NPOTB DONTBUILD CLOSED TREE r=rail
Jordan Lund <jlund@mozilla.com> - Mon, 01 Feb 2016 13:42:38 -0800 - rev 282617
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1219094 - releng - kill api-11 mozconfigs NPOTB DONTBUILD CLOSED TREE r=rail
900810a353c30e0ec8d15075110e5f9838cca7b1: Bug 1216150 - Mini-bustage fix for something I think I unintentionally qref'd into the final patch. r=bustage in a CLOSED TREE
Jeff Walden <jwalden@mit.edu> - Mon, 01 Feb 2016 13:37:27 -0800 - rev 282616
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1216150 - Mini-bustage fix for something I think I unintentionally qref'd into the final patch. r=bustage in a CLOSED TREE
c79d6954e4b1dc2779744cdec700eb0f209342cf: Bug 1241455 Send TLS Error Reports for subresources r=past, Gijs, mcmanus
Mark Goodwin <mgoodwin@mozilla.com> - Mon, 01 Feb 2016 11:18:50 +0000 - rev 282615
Push 17362 by cbook@mozilla.com at Tue, 02 Feb 2016 10:54:53 +0000
Bug 1241455 Send TLS Error Reports for subresources r=past, Gijs, mcmanus This patch makes use of the security reporter component (which hasn't landed yet - see blockers) to allow automatic TLS error reports to be sent directly from nsHttpChannel.cpp rather than sending them from browser.js. This allows failed connections for subresources to be reported. Some of the report sending from browser.js was retained to allow reports to be sent at the time a user enables reporting. This has been modified to also make use of the component. Since the patient is on the table, I've also taken the opportunity to remove the retry and status bits from aboutCertError.xhtml and aboutNetError.xhtml - which removes a bunch of code and simplifies things a bit. The mochitests have been modified to cope with the fact that the UI does not update with report sending / report failures - instead, success and failure are determined by examining the response seen from the server from within the test.
(0) -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip