I also add some missing data to the content version, namely the duration of time that ContentParent::SendLoadPlugin takes.
MozReview-Commit-ID: 8qSZopvY1D7
--HG--
extra : rebase_source : ca717c149a52ed1ece9ac0678dca0c284ab26c5d
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. So hopefully
this patch never lands because someone insists of fixing the underlying
problem instead. But if it does land, hopefully the workaround is
only temporary.
MozReview-Commit-ID: Gcq3Qna02iB
--HG--
extra : rebase_source : 2ccaa22eb85280cc8d322df87fb759e8dff67cf1
The main change is that we move AutoJSExceptionReporter up to before the first
place where we might throw an exception, so we report those exceptions before
returning. The change to use AutoEntryScript consistently is because all of
these callsites can run JS in practice, and it seems reasonable to allow them
to.
mContentParent is really just to be used while handling a synchronous
ContentParent::RecvLoadPlugin call when async plugin init turned on.
In any other context, using it will be unsafe.
This patch adds comments and assertions to ensure that this value isn't set
otherwise, and converts the one use of mContentParent outside of async plugin
init to use an alternative mechanism for identifying the content process.
MozReview-Commit-ID: Esgt1kj0MCt
--HG--
extra : rebase_source : 166b913b401582c6948e4b61efc102dc1b9c8d2f
dom/plugins/test/testplugin/nptest_macosx.mm:278:10: warning: will never be executed [-Wunreachable-code]
dom/plugins/test/testplugin/nptest_macosx.mm:307:10: warning: will never be executed [-Wunreachable-code]
dom/plugins/test/testplugin/nptest.cpp:697:7: warning: will never be executed [-Wunreachable-code]
dom/plugins/test/testplugin/nptest.cpp:2300:15: warning: will never be executed [-Wunreachable-code]
Modify the Mac sandbox to allow temporary files to be created in a
parent-specified subdirectory of NS_OS_TEMP_DIR. This is similar to the
Windows approach. The parent provides a UUID in a preference which is
used by the content process to form the subdirectory name.
MozReview-Commit-ID: 6BONpfZz8ZI
--HG--
extra : rebase_source : ad18e091918356a1a40c13f1453972b4512ad476
When turned on e10s, plugin process creates from chrome process. So content
process doesn't know current sandbox level. To rewrite wmode attribute on
contnet process by sandbox level >= 2, we should store sandbox level to
nsPluginTag.
MozReview-Commit-ID: DCQ5g7uCbJF
--HG--
extra : rebase_source : 7064f469e873ea1301e28faeab0bbb27613978db
Be warned. Do not attemp to change the .js "test" source code in ./js
They are meant to check
- the outdated 0666 octal constant is still parsed correctly,
- the outdated 0666 octal constant raises syntax error flag
in strict mode, etc.
So leave them alone.
They were disabled in bug 657569 because of a miscompilation from MSVC,
but back then, we were using one of 2005, 2008 or 2010 (not entirely
sure which). Even if it was the latter, there has been two releases of
MSVC since, if stopping at the one we're currently using.
Mike Hommey
Blake Kaplan
Dylan Roeh
Tooru Fujisawa
Aaron Klotz
Gregory Szorc
Jim Mathies
Ryan VanderMeulen
Christoph Kerschbaumer
Boris Zbarsky
Kyle Machulis
Wes Kocher
Drew Willcoxon
Mike de Boer
sakshi
Jonathan Griffin
Yury Delendik
Chris Peterson
Haik Aftandilian
Bogdan Postelnicu
Phil Ringnalda
Dão Gottwald
Carsten "Tomcat" Book
Makoto Kato
Mason Chang
Aidin Gharibnavaz
ISHIKAWA, Chiaki
Karl Tomlinson
Nicholas Nethercote