They're no longer in the spec, and we and Chrome have supported the up to date
versions for a while.
MozReview-Commit-ID: 3OBpPuua7GW
--HG--
extra : source : d9122e818c36fc0e2381ae469988a96324e5557d
I had meant to remove all of these in bug 1276132, but I missed a couple. We
should now check whether Widevine is enabled before hitting these code paths
by checking the preference.
MozReview-Commit-ID: FmAdlgbF0Py
--HG--
extra : source : 586eff45c5479c7efc86435add5f6e9edd5e43b0
extra : amend_source : 65a9902374155d9e3180f0510b1d1434b986dc83
1. If mHasUserInteraction MediaElement is false, don't run the TimeMarchesOn because the element is not played. 2. Update the activeCueList only in TimeMarchesOn(). 3. Run TimeMarchesOn() at the beginning of play. r=rillian
MozReview-Commit-ID: BhwsIfRm3B2
--HG--
extra : rebase_source : 9713d4f467f1d708f65a25e54435d0c6e8ff1816
The refresh driver may not be triggered regularly if the page is static.
In that case, we need to ensure a flush is scheduled for fullscreen
change, otherwise the page may get stuck.
MozReview-Commit-ID: c5FhqaIUQW
--HG--
extra : source : 10269de859e1a6b532ecd02fafff205365c51f2b
MockedOpen monkeypatches os.path.exists. Changes to MockedOpen
since this test code was written have made it more robust
making the extra monkeypatching in the test not necessary.
This change may not fix the test failure reported in the bug.
But at least it makes the test code simpler.
MozReview-Commit-ID: BnUr08leope
--HG--
extra : rebase_source : d8d721392c88883fddf7959ca40ea194f91483c9
Given the implementation of BaseMarionetteArguments.parse_known_args,
remove call to parser.parse_args in Marionette mach commands
(marionette-test, session-test,
firefox-ui-update, firefox-ui-functional,
external-media-tests).
Instead, create an argparse.Namespace from the already-parsed
arguments, and pass this to parser.verify_usage.
MozReview-Commit-ID: 20agrkhwlLF
--HG--
extra : rebase_source : 32b0df89c1fbc52af57884d6ba764502b64ac590
I think that we can drop nsIMEUpdatePreference::DontNotifyChangesCausedByComposition(), i.e., nsIMEUpdatePreference::NOTIFY_CHANGES_CAUSED_BY_COMPOSITION because it's now used only by TSFTextStore but TSFTextStore ignores if SelectionChangeDataBase::mCausedByComposition or TextChangeDataBase::mCausedOnlyByComposition is true (for supporting async changes in e10s mode). So, only issue is, dropping the flag might cause increasing computing TextChangeData cost during composition in TSF mode. However, now, it's already enough fast and even if it'd cause performance regression, we could add a hack with TextComposition's offset information. Therefore, we don't need to worry about the performance regression so seriously.
MozReview-Commit-ID: HNT3G4isONj
--HG--
extra : rebase_source : 164231023aa2a17ceab94d92fb49ba0a00dab429
Currently, all widgets request selection change notifications to IMEContentObserver. Additionally, IMEContentObserver needs to listen selection changes for caching latest selection for eQuerySelectedText. Therefore, it doesn't make sense to keep defining nsIMEUpdatePreference::NOTIFY_SELECTION_CHANGE.
If widgets didn't need selection change notifications, they could just ignore the unnecessary notifications.
Note that all widgets don't need selection change notifications if a plugin has focus and IMEContentObserver cannot observe selection changes in the plugin. Therefore, if IMEContentObserver is initialized with a plugin, it shouldn't listen selection changes (and doesn't need to notify widgets of selection changes).
MozReview-Commit-ID: FOVFFgA2nOz
--HG--
extra : rebase_source : 3e16d5023835f99f82934e754d2e7db70474f9ee
Jeff Gilbert
Sebastian Hengst
Ben Kelly
Carsten "Tomcat" Book
Nicolas Silva
Mantaroh Yoshinaga
Chris Pearce
Cervantes Yu
bechen
Xidorn Quan
Arthur Edelstein
Jessica Jong
John Dai
Jocelyn Liu
Marcos Caceres
Gregory Szorc
Anjana Vakil
Alexandre Lissy
Masatoshi Kimura
Kartikaya Gupta
JW Wang
Paul Adenot
Masayuki Nakano