f488247929060f747cd20e08c5fbb66841aa0443: turn off warnings about missing braces in gmp-clearkey draft
Nathan Froyd <froydnj@mozilla.com> - Wed, 26 Oct 2016 12:14:51 -0400 - rev 432804
Push 34429 by bmo:nfroyd@mozilla.com at Wed, 02 Nov 2016 20:25:31 +0000
turn off warnings about missing braces in gmp-clearkey MozReview-Commit-ID: GafOgYO6IwM
4ca432705fc81eb38d0ea8603a69ca8453798aca: jsoncpp build fix draft
Nathan Froyd <froydnj@mozilla.com> - Wed, 26 Oct 2016 12:14:19 -0400 - rev 432803
Push 34429 by bmo:nfroyd@mozilla.com at Wed, 02 Nov 2016 20:25:31 +0000
jsoncpp build fix MozReview-Commit-ID: 35xOb4AJwbq
216e8573b85b3c17868d64e2fd1cddd7e6bc4fc2: Bug 1310279 - add "wm" to Services shim; r?jdescottes draft
Tom Tromey <tom@tromey.com> - Thu, 20 Oct 2016 14:34:23 -0600 - rev 432802
Push 34428 by bmo:ttromey@mozilla.com at Wed, 02 Nov 2016 20:24:43 +0000
Bug 1310279 - add "wm" to Services shim; r?jdescottes MozReview-Commit-ID: 2uW8RM2ufaf
b5540015b5351438be59a2dc4f58d9d6e02b638f: Bug 1309935 - Add ability to find within select dropdown when over 40 elements r=jaws, mconley draft
TylerM <maklebus@msu.edu> - Wed, 02 Nov 2016 10:57:29 -0400 - rev 432801
Push 34427 by bmo:maklebus@msu.edu at Wed, 02 Nov 2016 20:15:41 +0000
Bug 1309935 - Add ability to find within select dropdown when over 40 elements r=jaws, mconley Search implemented for select dropdown options. List navigation takes keyboard input as before, until search field is focused. Pref added to enable search (dom.forms.selectSearch). MozReview-Commit-ID: HjXGY0FbgrO
6f2d25574cf0c0de146bae42f5acf6b5663e5cb7: Bug 1312477 - Post: remove arbitrary peek and max heights from BottomSheet menu r?sebastian draft
Andrzej Hunt <ahunt@mozilla.com> - Wed, 02 Nov 2016 21:13:19 +0100 - rev 432800
Push 34426 by ahunt@mozilla.com at Wed, 02 Nov 2016 20:14:04 +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
606582e7babca659e24e8fdd898657be6f1a9160: Bug 1312477 - Add popupmenu mode to AS context menu for use on tablet r?sebastian draft
Andrzej Hunt <ahunt@mozilla.com> - Wed, 02 Nov 2016 21:01:43 +0100 - rev 432799
Push 34426 by ahunt@mozilla.com at Wed, 02 Nov 2016 20:14:04 +0000
Bug 1312477 - Add popupmenu mode to AS context menu for use on tablet r?sebastian MozReview-Commit-ID: HCym4G8RtcU
49ebe98a0ce759da2554834355a2abd1a9b7e796: Bug 1312477 - Pre: refactor AS context menu to allow multiple view implementations r?sebastian draft
Andrzej Hunt <ahunt@mozilla.com> - Wed, 02 Nov 2016 20:57:05 +0100 - rev 432798
Push 34426 by ahunt@mozilla.com at Wed, 02 Nov 2016 20:14:04 +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
c9f931604d51e833be1255f4e5812beb2792d7fd: Bug 1312477 - Pre: increase touch-target size to Android UI guidelines r?sebastian draft
Andrzej Hunt <ahunt@mozilla.com> - Wed, 02 Nov 2016 20:58:26 +0100 - rev 432797
Push 34426 by ahunt@mozilla.com at Wed, 02 Nov 2016 20:14:04 +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
85defe58d3437461d04ce3b9aa2e860bc2dbcb4f: Bug 1299428 - Searching an URL looking string using a one-off button doesn't open a search result. r=adw draft
Marco Bonardo <mbonardo@mozilla.com> - Wed, 02 Nov 2016 18:32:38 +0100 - rev 432796
Push 34425 by mak77@bonardo.net at Wed, 02 Nov 2016 20:09:13 +0000
Bug 1299428 - Searching an URL looking string using a one-off button doesn't open a search result. r=adw MozReview-Commit-ID: FA9qkqLw5Cw
87119d3298b34e454bd0712510b8b612e975c67b: Bug 1299428 - Use more of BrowserTestUtils in urlbar tests. r=adw draft
Marco Bonardo <mbonardo@mozilla.com> - Mon, 31 Oct 2016 17:56:01 +0100 - rev 432795
Push 34425 by mak77@bonardo.net at Wed, 02 Nov 2016 20:09:13 +0000
Bug 1299428 - Use more of BrowserTestUtils in urlbar tests. r=adw MozReview-Commit-ID: DnM6PylbNv
f43b6c8e32da3ffbdd2b3d1b383c940f16296a26: Bug 1220362 - retry on dlopen.c errors. r?gbrown draft
Joel Maher <jmaher@mozilla.com> - Wed, 02 Nov 2016 15:59:10 -0400 - rev 432794
Push 34424 by bmo:jmaher@mozilla.com at Wed, 02 Nov 2016 19:59:36 +0000
Bug 1220362 - retry on dlopen.c errors. r?gbrown MozReview-Commit-ID: BL08acEIH99
c7ae634cfdf2d493085bbb6d7c552dff03856270: Bug 1313884 - Check if mTarget is null in CanvasRenderingContext2D::DrawImage
Ryan Hunt <rhunt@eqrion.net> - Tue, 01 Nov 2016 13:56:55 -0500 - rev 432793
Push 34424 by bmo:jmaher@mozilla.com at Wed, 02 Nov 2016 19:59:36 +0000
Bug 1313884 - Check if mTarget is null in CanvasRenderingContext2D::DrawImage
aa39c1a962ffa63c1c5017b8c824663dea930771: Bug 687787: support focusin/focusout based on webkit/blink r=smaug
Kevin Wern <kevin.m.wern@gmail.com> - Thu, 06 Oct 2016 21:39:53 -0400 - rev 432792
Push 34424 by bmo:jmaher@mozilla.com at Wed, 02 Nov 2016 19:59:36 +0000
Bug 687787: support focusin/focusout based on webkit/blink r=smaug Blink and webkit launch focusin after focus and focusout after blur. Despite this contradiction with the spec, it is best to mirror this new way, as there is little guidance or existing code to clarify implementation amiguities that can arise from the spec. If focus/blur is fired on a window or document, or the event triggers a change of focus, do not fire the corresponding focusin/focusout. Otherwise, always fire the corresponding event. Additionally, add a mochitest and a w3c-platform-test. MozReview-Commit-ID: AgQ8JBxKIqK
01927ad414ea0925f976b191c2db41a0d0152ae9: Backed out changeset 6c32452df00e (bug 1238305) for cpp test failures a=backout
Wes Kocher <wkocher@mozilla.com> - Wed, 02 Nov 2016 12:18:58 -0700 - rev 432791
Push 34424 by bmo:jmaher@mozilla.com at Wed, 02 Nov 2016 19:59:36 +0000
Backed out changeset 6c32452df00e (bug 1238305) for cpp test failures a=backout
0cb96d5b5a57709e54e59887d57a36225b0b115e: Backed out 2 changesets (bug 1314037) for win64 wpt(1) failures a=backout
Wes Kocher <wkocher@mozilla.com> - Wed, 02 Nov 2016 12:12:02 -0700 - rev 432790
Push 34424 by bmo:jmaher@mozilla.com at Wed, 02 Nov 2016 19:59:36 +0000
Backed out 2 changesets (bug 1314037) for win64 wpt(1) failures a=backout Backed out changeset 0223902c2353 (bug 1314037) Backed out changeset c9b3a1252363 (bug 1314037)
3898797a6267e6d0f84049258e261e207fafd4e5: Bug 1305977 - Use HarfBuzz ot-math API to parse the OpenType MATH table. r=jfkthame
Frédéric Wang <fred.wang@free.fr> - Wed, 02 Nov 2016 11:47:18 -0700 - rev 432789
Push 34424 by bmo:jmaher@mozilla.com at Wed, 02 Nov 2016 19:59:36 +0000
Bug 1305977 - Use HarfBuzz ot-math API to parse the OpenType MATH table. r=jfkthame
773aed2f801b27cbad3c031fc7aa747ea9b2c1ed: Backed out changeset 961a84574836 (bug 1305977) for multiscripts-1.html failures a=backout
Wes Kocher <wkocher@mozilla.com> - Wed, 02 Nov 2016 11:45:41 -0700 - rev 432788
Push 34424 by bmo:jmaher@mozilla.com at Wed, 02 Nov 2016 19:59:36 +0000
Backed out changeset 961a84574836 (bug 1305977) for multiscripts-1.html failures a=backout
6d9d913293cf60f8acbf438232331c37b8dfbc07: Bug 1308677 - Make PluginContent only show CtP doorhanger when no decoders can be found. r?blassey draft
Mike Conley <mconley@mozilla.com> - Wed, 02 Nov 2016 15:44:21 -0400 - rev 432787
Push 34423 by mconley@mozilla.com at Wed, 02 Nov 2016 19:54:49 +0000
Bug 1308677 - Make PluginContent only show CtP doorhanger when no decoders can be found. r?blassey MozReview-Commit-ID: 4Utu7HP0udG
02e6f07dd0d4fd5d7633c3a016bb22e89a1871a4: Bug 1020516 - Add timestamp messages when dumping buffered messages in mochitest, r?ted draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 02 Nov 2016 13:42:58 -0400 - rev 432786
Push 34422 by ahalberstadt@mozilla.com at Wed, 02 Nov 2016 19:47:10 +0000
Bug 1020516 - Add timestamp messages when dumping buffered messages in mochitest, r?ted When dumping buffered messages in mochitest, this adds a new log line for every second's worth of messages. Alternatively we could print the timestamp in brackets at the end of each buffered message, but I found that in practice there tends to be many log messages generated each second. This looks better for that case, but will look much worse if logs are generated more than a second apart. I would be ok with either method. MozReview-Commit-ID: Jkd9hOlmiGZ
a86ad1d51eb92bfed2170d21429b289fcc8d5105: Bug 1020516 - Only buffer mochitest log messages that happen between a TEST-START/TEST-END, r?ted draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 02 Nov 2016 13:42:58 -0400 - rev 432785
Push 34422 by ahalberstadt@mozilla.com at Wed, 02 Nov 2016 19:47:10 +0000
Bug 1020516 - Only buffer mochitest log messages that happen between a TEST-START/TEST-END, r?ted I believe the current behaviour of buffering messages outside of a test is wrong. For example: 1. INFO logged -> gets buffered 2. TEST-START logged -> doesn't get buffered 3. Test fails and buffer dumped -> INFO looks like it happened after the TEST-START I think this is very confusing as developers trying to debug a test will think that INFO message is happening somewhere inside their test when in reality it isn't. MozReview-Commit-ID: Jkd9hOlmiGZ
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip