839bfae581baff576e36f7701c25c8baa48289d0: Bug 687787 - Support focusin/focusout events r=smaug draft
Kevin Wern <kevin.m.wern@gmail.com> - Sun, 20 Mar 2016 04:39:32 -0700 - rev 374279
Push 19976 by kevin.m.wern@gmail.com at Thu, 02 Jun 2016 04:58:01 +0000
Bug 687787 - Support focusin/focusout events r=smaug Add support for focusin and focusout in DOM. The event sequence is either: (for focuses) - focusin - focus or (for refocuses) - focusout - focusin - blur - focus (for unfocuses) - focusout - blur Additionally, add the necessary attributes to ensure only one focus occurs as the result of a series of events. Also ensure that focusout doesn't recurse if focus() is called in an event callback. Include mochitest and web-platform-tests. MozReview-Commit-ID: LGPPEC3WH55
8092a3457020ca249f575e97067a654017c72cc1: Bug 687787 - Support focusin/focusout events r=smaug draft
Kevin Wern <kevin.m.wern@gmail.com> - Sun, 20 Mar 2016 04:39:32 -0700 - rev 374278
Push 19975 by kevin.m.wern@gmail.com at Thu, 02 Jun 2016 04:48:53 +0000
Bug 687787 - Support focusin/focusout events r=smaug Add support for focusin and focusout in DOM. The event sequence is either: (for focuses) - focusin - focus or (for refocuses) - focusout - focusin - blur - focus (for unfocuses) - focusout - blur Additionally, add the necessary attributes to ensure only one focus occurs as the result of a series of events. Also ensure that focusout doesn't recurse if focus() is called in an event callback. Include mochitest and web-platform-tests. MozReview-Commit-ID: LGPPEC3WH55
c8186e96a8e1298be725331e6da56417301cd20b: Bug 1271345 Fix brower.download.download() on blob: urls r?kmag draft
Andrew Swan <aswan@mozilla.com> - Tue, 31 May 2016 11:42:41 -0700 - rev 374277
Push 19974 by aswan@mozilla.com at Thu, 02 Jun 2016 04:19:29 +0000
Bug 1271345 Fix brower.download.download() on blob: urls r?kmag Calling download() on a blob URL was failing in schema validation since we weren't propagating the extension principal all the way to the call to scriptSecurityManager.checkLoadURI... MozReview-Commit-ID: JgEnQ6yxO4P
40690ce53ad83b463ee3eef35f13b56b428c67bd: Bug 1275906 part.2 TextComposition should use IMEContentObserver for sending NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED if the editor which has the composition is in the active IMEContentObserver r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 01 Jun 2016 22:14:41 +0900 - rev 374276
Push 19973 by masayuki@d-toybox.com at Thu, 02 Jun 2016 04:17:43 +0000
Bug 1275906 part.2 TextComposition should use IMEContentObserver for sending NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED if the editor which has the composition is in the active IMEContentObserver r?smaug For sending NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED after the other change notifications which was caused by the user input, we need to use IMEContentObserver::IMENotificationSender because it sends the notifications when it's safe to do it. This patch makes TextComposition use IMEContentObserver to send the notification. However, if there is no active IMEContentObserver, e.g., composition events are fired on unfocused window, TextComposition sends it by itself (same as current implementation). If IMEContentObserver stops observing when it has pending NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED, it cannot send the notification (i.e., it is discarded completely in such case). However, in such case, IMEContentObserver sends NOTIFY_IME_OF_BLUR. So, anyway, native IME handler should treat the blur notification as it including NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED. On the other hand, we're buggy if composition events are fired in non-active window. Even in such case, IMEContentObserver should be created for active editor in each document and it notifies IME of the changes. But this is out of the scope of this bug. MozReview-Commit-ID: 7Q0ZsJTh4hX
d3cd26e907c314899bec6367f9d2e863a8861840: Bug 1275906 part.1 Rename NOTIFY_IME_OF_COMPOSITION_UPDATE to NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 31 May 2016 11:39:15 +0900 - rev 374275
Push 19973 by masayuki@d-toybox.com at Thu, 02 Jun 2016 04:17:43 +0000
Bug 1275906 part.1 Rename NOTIFY_IME_OF_COMPOSITION_UPDATE to NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED r?m_kato It's not clear to me what NOTIFY_IME_OF_COMPOSITION_UPDATE means only from the name. For making the name clearer, this patch renames it to NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED and add some explanation to the definition. MozReview-Commit-ID: 8ySYCNJ1Ytz
ad40a29d0ceb8ea44eba61b28a86d89199e2d8f6: Bug 1276132 - Make more Widevine class constructors explicit to keep gcc happy. r=jwwang draft
Chris Pearce <cpearce@mozilla.com> - Tue, 31 May 2016 12:05:24 +1200 - rev 374274
Push 19972 by cpearce@mozilla.com at Thu, 02 Jun 2016 04:16:40 +0000
Bug 1276132 - Make more Widevine class constructors explicit to keep gcc happy. r=jwwang Fixes compile errors on Linux when Widevine is compiled. MozReview-Commit-ID: 19qQw02CqdQ
c198d6613c04df0d9889a6121606498e883ff607: Bug 1276132 - Don't show EME 'enable' UI for non-visible keysystems. r=gijs draft
Chris Pearce <cpearce@mozilla.com> - Tue, 31 May 2016 12:04:12 +1200 - rev 374273
Push 19972 by cpearce@mozilla.com at Thu, 02 Jun 2016 04:16:40 +0000
Bug 1276132 - Don't show EME 'enable' UI for non-visible keysystems. r=gijs This means we'll only show the EME UI for keysystems that are explicitly turned on in the build config, or those that are enabled after the build via prefs. MozReview-Commit-ID: 7VTp1BJSZFy
ba7a526411567db90791a55981d79a33b0e0d1bb: Bug 1276132 - Remove use of #ifdef MOZ_{KEYSYSTEM}_EME in dom/media code. r=jwwang draft
Chris Pearce <cpearce@mozilla.com> - Tue, 31 May 2016 11:00:55 +1200 - rev 374272
Push 19972 by cpearce@mozilla.com at Thu, 02 Jun 2016 04:16:40 +0000
Bug 1276132 - Remove use of #ifdef MOZ_{KEYSYSTEM}_EME in dom/media code. r=jwwang Instead of controlling visibility of EME keysystems by build config, do it by preference. This means keysystems can be turned on easier. MozReview-Commit-ID: Ky1zrHPubOJ
6011d514262b561485bf0bb0231ba5fda2a166fc: Bug 1276132 - Rename media.gmp-*.forcevisible to media.gmp-*.visible, and set it when keysystems are enabled. r?spohl draft
Chris Pearce <cpearce@mozilla.com> - Tue, 31 May 2016 10:59:44 +1200 - rev 374271
Push 19972 by cpearce@mozilla.com at Thu, 02 Jun 2016 04:16:40 +0000
Bug 1276132 - Rename media.gmp-*.forcevisible to media.gmp-*.visible, and set it when keysystems are enabled. r?spohl Repurpose the media.gmp-*.forcevisible pref to control whether the corresponding GMP is visible in the addons manager UI. The pref has to be true for the GMP to be usable. The pref is enabled and not hidden when the corresponding EME keysystem is enabled in the mozconfig. This means users can turn on EME without needing to recompile their build; they just need to create a hidden pref. This will be useful for CDM developers, and users on platforms where we've not enabled EME yet but users want to test it (Linux). We also need to change the GMPUtils.isPluginHidden() accessor so that plugins are considered hidden if the "visible" pref is false OR we're on an unsupported platform. This ensures that we must be on a supported OS and the visibility pref is true before GMPs appear in the addon list. A consequence of the isPluginHidden() change is that we also need to add a "force-supported" pref to override the checks that refuse to load the GMPs on various platform versions, so that the unit tests pass. MozReview-Commit-ID: h6CwLDkvFW
87676e5b6db574ea9f5b68b43b9d5eaeabaf120a: Bug 1257727, 1257729 - Update WebM handling to deal with encrypted WebMs r?jya draft
Bryce Van Dyk <bvandyk@mozilla.com> - Fri, 27 May 2016 14:34:54 +1200 - rev 374270
Push 19971 by bvandyk@mozilla.com at Thu, 02 Jun 2016 04:15:11 +0000
Bug 1257727, 1257729 - Update WebM handling to deal with encrypted WebMs r?jya - WebMDemuxer will read crypto information from WebM metadata. - WebMDemumer adds crypto information to samples. - WebMDemuxer can now return encryption info from GetCrypto(). - WebMDexmuer will not attempt to peek encrypted frames as it will give back garbage data. This means resolution changes internal to encrypted WebM files will not work. - WebMDecoder now exposes a single string version of CanHandleMediaType. This is done in the same way as the Mp4Decoder, so that the future update to MediaKeySystemAccess for WebM handling can maintain the same conventions. MozReview-Commit-ID: CU3JVi3t7Vn
318cf49475793b1cd2b9a2838b1123b153fdc278: Bug 1275906 part.2 TextComposition should use IMEContentObserver for sending NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED if the editor which has the composition is in the active IMEContentObserver r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 01 Jun 2016 22:14:41 +0900 - rev 374269
Push 19970 by masayuki@d-toybox.com at Thu, 02 Jun 2016 04:13:18 +0000
Bug 1275906 part.2 TextComposition should use IMEContentObserver for sending NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED if the editor which has the composition is in the active IMEContentObserver r?smaug For sending NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED after the other change notifications which was caused by the user input, we need to use IMEContentObserver::IMENotificationSender because it sends the notifications when it's safe to do it. This patch makes TextComposition use IMEContentObserver to send the notification. However, if there is no active IMEContentObserver, e.g., composition events are fired on unfocused window, TextComposition sends it by itself (same as current implementation). If IMEContentObserver stops observing when it has pending NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED, it cannot send the notification (i.e., it is discarded completely in such case). However, in such case, IMEContentObserver sends NOTIFY_IME_OF_BLUR. So, anyway, native IME handler should treat the blur notification as it including NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED. On the other hand, we're buggy if composition events are fired in non-active window. Even in such case, IMEContentObserver should be created for active editor in each document and it notifies IME of the changes. But this is out of the scope of this bug. MozReview-Commit-ID: 7Q0ZsJTh4hX
d538360829261993ef03a48fb0f822cfe0f9cdca: Bug 1275906 part.1 Rename NOTIFY_IME_OF_COMPOSITION_UPDATE to NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 31 May 2016 11:39:15 +0900 - rev 374268
Push 19970 by masayuki@d-toybox.com at Thu, 02 Jun 2016 04:13:18 +0000
Bug 1275906 part.1 Rename NOTIFY_IME_OF_COMPOSITION_UPDATE to NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED r?m_kato It's not unclear to me what NOTIFY_IME_OF_COMPOSITION_UPDATE means only with the name. For making the name clearer, this patch renames it to NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED and add some explanation to the definition. MozReview-Commit-ID: 8ySYCNJ1Ytz
f3f7a4271cff0e185aa6ad88d68b25ef673210c0: Bug 1276406 Remove "ime-enabled-state-changed" notification completely r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 31 May 2016 18:39:43 +0900 - rev 374267
Push 19970 by masayuki@d-toybox.com at Thu, 02 Jun 2016 04:13:18 +0000
Bug 1276406 Remove "ime-enabled-state-changed" notification completely r?smaug "ime-enabled-state-changed" notification was implemented for Android in bug 603848 but nobody currently observes this notification. Therefore, we can stop notify the observer service of this. MozReview-Commit-ID: 3TNHf1xWo2l
63ccee5858a3bb9cce2a5423892cc77b64262322: Bug 1174900 - Capture doorhanger password field should stay disabled for master password users;r?MattN draft
gasolin <gasolin@gmail.com> - Fri, 13 May 2016 11:50:08 +0800 - rev 374266
Push 19969 by bmo:gasolin@mozilla.com at Thu, 02 Jun 2016 04:04:38 +0000
Bug 1174900 - Capture doorhanger password field should stay disabled for master password users;r?MattN MozReview-Commit-ID: 4noJdsx6NYN
c77f5610b2a890c8f4abfa23418521c9b52bf616: Bug 1277134 - Add built-in fsmonitor support for Mercurial version>=3.8. r=gps
Jeremy Chen <jeremychen@mozilla.com> - Wed, 01 Jun 2016 16:40:55 +0800 - rev 374265
Push 19969 by bmo:gasolin@mozilla.com at Thu, 02 Jun 2016 04:04:38 +0000
Bug 1277134 - Add built-in fsmonitor support for Mercurial version>=3.8. r=gps The hgwatchman project has been renamed to fsmonitor and has been moved into Mercurial core, as of version 3.8. Accordingly, for Mercurial >= 3.8, we shall skip installing hgwatchman but just set fsmonitor in hgrc file instead. DONTBUILD (NPOTB) MozReview-Commit-ID: 426rla5riCM
24bd574ecbf0c8630290fc81f76e6a928d3ee8dd: Bug 1277156 - TaskbarPreview::Disable should check whether window is destroyed. r=jimm
Makoto Kato <m_kato@ga2.so-net.ne.jp> - Wed, 01 Jun 2016 14:30:23 +0900 - rev 374264
Push 19969 by bmo:gasolin@mozilla.com at Thu, 02 Jun 2016 04:04:38 +0000
Bug 1277156 - TaskbarPreview::Disable should check whether window is destroyed. r=jimm TaskbarTabPreview object will be released by GC. So when Disable method is called, window may already destroyed. So we should check whether window is destroyed. MozReview-Commit-ID: MGz3JmDh37
199560989621a1fb7790aa9f44cfb07aea49a755: Merge m-c to inbound, a=merge
Wes Kocher <wkocher@mozilla.com> - Wed, 01 Jun 2016 17:17:15 -0700 - rev 374263
Push 19969 by bmo:gasolin@mozilla.com at Thu, 02 Jun 2016 04:04:38 +0000
Merge m-c to inbound, a=merge
bdc32a7922924aeff034cd5c47580cb493b922cb: Bug 887934 - Add closed caption button to video control. r?jaws draft
Ray Lin <ralin@mozilla.com> - Tue, 24 May 2016 14:31:54 +0800 - rev 374262
Push 19968 by bmo:ralin@mozilla.com at Thu, 02 Jun 2016 03:51:41 +0000
Bug 887934 - Add closed caption button to video control. r?jaws MozReview-Commit-ID: 7oWXBKWRtwy
eba1ba87dc2c1ef8e766f595987687d5246f0b51: Bug 1275165 - notifications.onClicked not being triggered, r?kmag draft
Bob Silverberg <bsilverberg@mozilla.com> - Wed, 01 Jun 2016 23:42:04 -0400 - rev 374261
Push 19967 by bmo:bob.silverberg@gmail.com at Thu, 02 Jun 2016 03:44:07 +0000
Bug 1275165 - notifications.onClicked not being triggered, r?kmag Change the value of the textClickable argument passed into nsIAlertsService.showAlertNotification to be `true` MozReview-Commit-ID: 7BqwUnt8ZK3
dd910e642e7bb2101fc0cc1c3dc4255f6dec88db: Bug 1274559 - Type error for parameter options (Unexpected property "buttons") for notifications.create, r?kmag draft
Bob Silverberg <bsilverberg@mozilla.com> - Mon, 30 May 2016 14:32:40 -0400 - rev 374260
Push 19966 by bmo:bob.silverberg@gmail.com at Thu, 02 Jun 2016 03:24:47 +0000
Bug 1274559 - Type error for parameter options (Unexpected property "buttons") for notifications.create, r?kmag MozReview-Commit-ID: FqjXfG2te5J
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip