a14ca8dbcc4b3e9475273f9327c4826e6b3a9130: Bug 1312719 - Clear icon by setIcon with null drawable before setIcon with resId, r=sebastian
maliu <max@mxli.us> - Sat, 05 Nov 2016 19:18:59 +0800 - rev 321592
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1312719 - Clear icon by setIcon with null drawable before setIcon with resId, r=sebastian MozReview-Commit-ID: LTUMIoANQw7
c8bca2404d0b9c6ef85cf0e4197dea3405f9447f: Bug 1315794 - migrate aboutdebugging to React 15.3.2;r=linclark
Julian Descottes <jdescottes@mozilla.com> - Mon, 07 Nov 2016 22:30:03 +0100 - rev 321591
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1315794 - migrate aboutdebugging to React 15.3.2;r=linclark Use ReactDOM.render instead of React.render (same for unmountComponentAtNode) Update tests to observe both childList and characterData mutations when expecting only text changes. MozReview-Commit-ID: ILTgypkpZRz
342db7014f26bdf8138c0670fdc808dbd370c0ef: Bug 1307905 - Ignore irrelevant properties in stub generation; r=linclark
Nicolas Chevobbe <chevobbe.nicolas@gmail.com> - Tue, 25 Oct 2016 20:16:50 +0200 - rev 321590
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1307905 - Ignore irrelevant properties in stub generation; r=linclark This can be tested by inserting a new stub in first position, in order to change the actor id on the existing stubs, and then check in the resulting diff that actor id, timestamp and timer properties are not modified. MozReview-Commit-ID: K5enQ5cF7RR
e35ee6e46109004db4abf0ad805f5518036ca12b: Bug 1313406 - Enable DTMF by default; r=jesup
Dan Minor <dminor@mozilla.com> - Mon, 07 Nov 2016 11:50:13 -0500 - rev 321589
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1313406 - Enable DTMF by default; r=jesup MozReview-Commit-ID: JUGU2JCPIah
7348925c1148ebc2f925c9a64867e2f91e2db883: Bug 1315514 - Bookmark keywords are still broken for POST forms. r=adw
Marco Bonardo <mbonardo@mozilla.com> - Mon, 07 Nov 2016 14:58:49 +0100 - rev 321588
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1315514 - Bookmark keywords are still broken for POST forms. r=adw MozReview-Commit-ID: 3lrRbZVtgii
e7aa936d8b6e3707a29665d9eb6623d21ff5deea: Bug 1299216 - Wait for process exit first before checking for crashes. r=automatedtester
Henrik Skupin <mail@hskupin.info> - Tue, 01 Nov 2016 10:48:25 +0100 - rev 321587
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1299216 - Wait for process exit first before checking for crashes. r=automatedtester MozReview-Commit-ID: 8U48dNHoFmi
d57d7ada1080b190a6415134f4d2dab55e382f86: Bug 1299216 - Remove always parameter from do_process_check decorator. r=automatedtester
Henrik Skupin <mail@hskupin.info> - Wed, 21 Sep 2016 12:57:50 +0200 - rev 321586
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1299216 - Remove always parameter from do_process_check decorator. r=automatedtester Removing the always parameter which is kinda useless here. Originally it was added to call check_for_crash() in case of a MarionetteException happening. But such an exception is never thrown in case of crashes. It will always be an IOError. So lets get it removed and ensure we call check_for_crashes() in all the cases, and can feed the crash status into the call to handle_socket_failure(). MozReview-Commit-ID: JeK3X7voocD
32b908ad1b02660ff9bce79cbae9b8b4e5515a94: Bug 1299216 - Enhance handling of crashes in Marionette. r=automatedtester
Henrik Skupin <mail@hskupin.info> - Wed, 02 Nov 2016 13:49:32 +0100 - rev 321585
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1299216 - Enhance handling of crashes in Marionette. r=automatedtester There are currently various issues in Marionette which cause extra and unnecessary logging output in case of chrome and content crashes. Especially the latter ones are not easy to discover. This patch makes the following improvements: * Correctly mark process crashes as IOError test failure. Until now we have only used the "Process has been closed" message, which does not correctly cover it, especially not if the process shutdown without a crash. * Allow changing the socket_timeout for the socket client. This was mainly necessary to allow unit tests to run faster. * Collect the number of crashes so it's known even later if the process has been crashed during the current session. It also fixes the case when check_for_crash() gets called twice, and for the second time False is returned which will trigger an invalid code path. * Reduce code duplication when destroying a session. * Adding a unit test to verify the correct behavior for chrome and content crashes. MozReview-Commit-ID: KdUQuJqFRli
8463d0e5bf289bd05ed23efddb119eee82ff6c03: Bug 1299216 - Make use of MOZ_CRASHREPORTER_SHUTDOWN environment variable in Marionette. r=automatedtester
Henrik Skupin <mail@hskupin.info> - Wed, 26 Oct 2016 12:43:42 +0200 - rev 321584
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1299216 - Make use of MOZ_CRASHREPORTER_SHUTDOWN environment variable in Marionette. r=automatedtester MozReview-Commit-ID: 88NhfqMGPXF
46fd1d89a918e2af60c2dfe8284925e30976c495: Bug 1299216 - Don't care about socket not connected for sock.shutdown() call. r=automatedtester
Henrik Skupin <mail@hskupin.info> - Wed, 21 Sep 2016 16:04:49 +0200 - rev 321583
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1299216 - Don't care about socket not connected for sock.shutdown() call. r=automatedtester MozReview-Commit-ID: 9DXLY66KqTg
7c0bdd869d2a58bbbad65d8bd1952ee0f39caf54: Bug 1299216 - Bump mozrunner version to 6.13. r=ahal
Henrik Skupin <mail@hskupin.info> - Wed, 28 Sep 2016 23:29:40 +0200 - rev 321582
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1299216 - Bump mozrunner version to 6.13. r=ahal MozReview-Commit-ID: 2hCytAyqfsp
6ec047c4e48e94fefb428779427591b22a01bb36: Bug 1299216 - [mozrunner] check_for_crashes() has to return the crash count since its last invocation. r=ahal
Henrik Skupin <mail@hskupin.info> - Wed, 21 Sep 2016 12:57:50 +0200 - rev 321581
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1299216 - [mozrunner] check_for_crashes() has to return the crash count since its last invocation. r=ahal Adapt check_for_crashes() for latest mozcrash changes, which returns the number of crashes for both log_crashes() and check_for_crashes() now. Also the runner should accumulate the number of crashes so it will be known at any time how many times the process has been crashed. MozReview-Commit-ID: Dl9FlH1TalH
d58be05673a2f2ef4e1db32193611d37f1da470c: Bug 1299216 - [mozcrash] Count crash reports in check_for_crashes and bump version to 1.0. r=ahal
Henrik Skupin <mail@hskupin.info> - Wed, 28 Sep 2016 23:26:19 +0200 - rev 321580
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1299216 - [mozcrash] Count crash reports in check_for_crashes and bump version to 1.0. r=ahal Currently check_for_crashes() behaves differently compared to log_crashes(), whereby it only returns a boolean if a crash has been detected but not the amount of crash reports found. We should make sure that both methods behave the same. Given that this change might affect consumers, we should have a major version bump for the new release. MozReview-Commit-ID: LiPaozJL5NF
9af814b282fa915ee95329443ee42cc46943a863: Bug 1312434 - add ContentDescription to Activity Stream menus and topsites r=sebastian
Andrzej Hunt <ahunt@mozilla.com> - Fri, 04 Nov 2016 10:55:54 +0100 - rev 321579
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1312434 - add ContentDescription to Activity Stream menus and topsites r=sebastian MozReview-Commit-ID: AvkG5OVSBsj
8e56f56c09a1bc1aceeaee1d6b277f4bcf021ce5: Bug 1312434 - Move Highlights title into separate RV item for better accessibility traversal r=sebastian
Andrzej Hunt <ahunt@mozilla.com> - Fri, 04 Nov 2016 10:53:45 +0100 - rev 321578
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1312434 - Move Highlights title into separate RV item for better accessibility traversal r=sebastian By default, a TextView within e.g. a RelativeLayout will be used as the description for the entire layout. I.e. traversal of the RecyclerView would begin with the Highlights title being read, and the entire toppanel (i.e. TopSites + the Highlights title) being focused, followed by traversing the TopSites pager. Instead we want to make sure TopSites are traversed _before_ getting to the highlights title. MozReview-Commit-ID: IIrts6vGouK
8e7eaf50e29406ba4dd5650bccad7b44751f63cc: Bug 1311599 - Disable hsts tests on linux32-debug only. r=kmckinley
Joel Maher <jmaher@mozilla.com> - Mon, 07 Nov 2016 14:51:45 -0500 - rev 321577
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1311599 - Disable hsts tests on linux32-debug only. r=kmckinley MozReview-Commit-ID: 2V5Xrfpwy3a
ee67814f9015f33e893caefe9c8bad0b4daa46f4: Bug 1312477 - Post: remove arbitrary peek and max heights from BottomSheet menu r=sebastian
Andrzej Hunt <ahunt@mozilla.com> - Wed, 02 Nov 2016 21:13:19 +0100 - rev 321576
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1312477 - Post: remove arbitrary peek and max heights from BottomSheet menu r=sebastian Setting the max height is completely arbitrary, and largely unnecessary - I think it's better to let the bottom automatically handle this until we know more about how the bottom sheet is perceived by real users. The peek height is similarly arbitrary - we'll probably want to discuss a good default height algorithm with UX, but setting an arbitrary hardcoded value seems wrong, especially since it doesn't behave well in landscape mode. BottomSheetDialog already does an acceptable job of finding a default peek height. MozReview-Commit-ID: LyAYzcytR6H
ffdf65db6dba6bbc5eb3e62cdc869746371fdca6: Bug 1312477 - Add popupmenu mode to AS context menu for use on tablet r=sebastian
Andrzej Hunt <ahunt@mozilla.com> - Wed, 02 Nov 2016 21:01:43 +0100 - rev 321575
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1312477 - Add popupmenu mode to AS context menu for use on tablet r=sebastian MozReview-Commit-ID: HCym4G8RtcU
522f6a80deadca7229e77a39babe6224e6bc8b07: Bug 1312477 - Pre: refactor AS context menu to allow multiple view implementations r=sebastian
Andrzej Hunt <ahunt@mozilla.com> - Wed, 02 Nov 2016 20:57:05 +0100 - rev 321574
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1312477 - Pre: refactor AS context menu to allow multiple view implementations r=sebastian This is in preparation for having a popup menu on tablets. MozReview-Commit-ID: 14thIuhRkgB
594d5fc4d75c0550defed9d336f8e20a4e6e0302: Bug 1312477 - Pre: increase touch-target size to Android UI guidelines r=sebastian
Andrzej Hunt <ahunt@mozilla.com> - Wed, 02 Nov 2016 20:58:26 +0100 - rev 321573
Push 21 by maklebus@msu.edu at Thu, 01 Dec 2016 06:22:08 +0000
Bug 1312477 - Pre: increase touch-target size to Android UI guidelines r=sebastian 48dp is the minimum touch target size as suggested in the Android UI guidelines: https://developer.android.com/design/patterns/accessibility.html A similar recommendation is made in: https://material.google.com/layout/metrics-keylines.html#metrics-keylines-touch-target-size MozReview-Commit-ID: 9ybgjSOfD2J
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 tip