This MANIFEST.in contained the wrong file name,
external-media-tests-requirements.txt rather than requirements.txt.
MozReview-Commit-ID: A0zJihjoxzf
--HG--
extra : rebase_source : ddc462d754d234af04ed5a37885b89f9187a3942
In general, using an AutoJSAPI inited with an object is NOT the same as using
AutoSafeJSContext (or AutoJSAPI inited without an object) and then entering the
compartment of the object: the former will report exceptions to the global of
the object as it comes off the stack, while the latter will not. This only
really matters if we have an object from a window or worker global and hence
might fire error events, or report internal stuff to the web console.
The changes to initing with an object made in this bug are OK for the following
reasons:
1) dom/base/Console.cpp: Always clears its exception before coming off the stack.
2) dom/base/nsDOMClassInfo.cpp: Inits with a non-web global.
3) dom/base/nsFrameMessageManager.cpp: Inits with a non-web global.
4) dom/media/MediaPermissionGonk.cpp: We probably want the caller to notice if
anything here throws.
5) dom/xbl/nsXBLPrototypeBinding.cpp: Inits with a non-web global.
6) dom/xul/nsXULElement.cpp: Inits with a non-web global.
7) extensions/pref/autoconfig/src/nsJSConfigTriggers.cpp: Inits with a non-web global.
8) ipc/testshell/XPCShellEnvironment.cpp: Inits with a non-web global.
mDestination is cleared during unlink, which means that after that point the
window can't do much with the AudioContext, nor should need to do so.
MozReview-Commit-ID: E45aCpEfJEu
--HG--
extra : rebase_source : cafd502552b7126bcdddc2544c4c28c1b62a701f
The mac decoder when used on intel GPU gives bad performance due to locking. Increasing the queue size allows to alleviate most problems.
MozReview-Commit-ID: 3yQ3btiMqvk
--HG--
extra : rebase_source : 17951db2769b2cd56742ba420f08b3f5ebc2436d
As part of unblocking building with VS2015u1 in automation, I'm mass
disabling compiler warnings that are turned into errors. This is not
the preferred mechanism to fix compilation warnings, of course.
Given that the warning is in WebRTC which is third party code, there
isn't much we can do about the warning. However, Google is building
Chrome with Visual Studio 2015, so I wouldn't be surprised if this
were fixed upstream or will be fixed upstream. Then again, we allow
warnings when building WebRTC. So perhaps not.
MozReview-Commit-ID: G6JP9fkCzfn
--HG--
extra : rebase_source : bf5c9a049230bb8e483f6a85bdbc2ca20eb3ab45
While almost identical to video/mp4, quicktime files often use codecs that we don't support: in particular MPEG4 part 2 and amr audio.
If a plugin exists and is enabled, prefer it to handle those files.
We only do so when opening the file directly. Media in <video> element will always play natively.
MozReview-Commit-ID: 1yPpzfDaCfT
--HG--
extra : rebase_source : 4c66eb0fd81a288f4c8eed643c79cf9851bd4273
Add tests to exercise seeking in cueless WebMs. These tests reproduce a subset
of the test_seek tests, namely the first 3. These tests have been added
separately from the test_seek ones to avoid additional logic required to handle
cueless WebMs in such test. Once random seeking for cueless WebMs is
implemented then these cases can be easily rolled into the existing test_seek
cases by moving the cueless WebM into the appropriate test array in the
manifest -- after which these tests can be removed.
MozReview-Commit-ID: DNwiSmMmALQ
MediaDecoder previously had 3 states within GetSeekable(), media is either
seekable, seekable but not supported by transport, or not seekable. Due to
changes to make cueless webms playable, a 4th option is needed: a file that is
not fully seekable, but may support seeking from the transport, such as these
webms, should only be seekable in the buffered range.
MozReview-Commit-ID: ISeFkngtrGU
Previously if a seek time is specified outside of the buffered range for
certain WebMs (particularly those without cues) the WebMDemuxer would fail out
of SeekInternal() with an error code. However, this would lead to issues due to
inconsistent state (recovery was not made from a failed seek). This change
attemps to address this by instead seeking to the final available cluster.
MozReview-Commit-ID: GZLPZDWLcT1
