MozReview-Commit-ID: BDyuSdNALvH

Bug 1370155 - Remove fullscreen mode in basic compositor video test to prevent intermittent problem. r=jmaher

MozReview-Commit-ID: IO5vS3uzj6g

--HG--
extra : rebase_source : 8ca77acd02c6cdb9f5cce9e43dcd5428a3ca2b07

servo: Merge #17179 - shrink Rule and store all heap-allocated selector data inline (from bholley:one_selector_allocation); r=emilio

https://bugzilla.mozilla.org/show_bug.cgi?id=1370107

Source-Repo: https://github.com/servo/servo
Source-Revision: 74ea8ce3ed6aa3d7edfe05924f196ccbe57daed6

--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : a8c3994ae54b1775686552f549605a7fc2ba5646

ProfilerStackFrameRAII and ProfilerStackFrameDynamicRAII are very similar; the
latter lets a dynamic string be specified as well (and lacks the
MOZ_GUARD_OBJECT stuff, for no good reason).

This patch does the following.

- Removes ProfilerStackFrameDynamicRAII, and adds a dynamic string to
  ProfilerStackFrameRAII. It also reorders the constructor's arguments to match
  the field ordering of ProfileEntry. There aren't many usage sites so these
  changes don't affect many places.

- With that done, there is only a single callsite for each of
  profiler_call_enter() and profiler_call_exit(), so the patch also inlines and
  removes them.

These annotations aren't doing anything useful. The important thing with
the PseudoStack is that, during pushes, the stack pointer incrementing happens
after the new entry is written, and this is ensured by the stack pointer being
Atomic.

The patch also improves the comments on PseudoStack.

--HG--
extra : rebase_source : 100f8a5e4b750c15fac66175550c4c284a141f16

MozReview-Commit-ID: EiG9icZCZ3x

MozReview-Commit-ID: Cb3YlCdVhQr

--HG--
extra : rebase_source : 3ed4d5a41898ead386f8a75b0d2f7be1899cf767

Bug 1353356 - Add rematerialized frames to the table on JitActivation after rematerialization succeeds. (r=jandem)

There are a bunch of invalid Cargo.toml files that some python stuff uses for
testing, but these cause errors out of cargo when we point to one of the SM
source tarballs as a git dependency. Easiest workaround is to not include any
non-SpiderMonkey Cargo.toml files in the source tarballs.

MozReview-Commit-ID: 1wLiG2Sq3g

Bug 1367487: Change bundle name (CFBundleName) of content process on OSX/macOS to differentiate it from the Firefox bundle name. r=mstange,ted

Bug 1370025 P4 Use FiringId validity in TimeoutManager::Timeouts::Insert() and ::ResetTimersForThrottleReduction(). r=ehsan

--HG--
extra : rebase_source : e7c27185c671f8d2eae81ddfc66318c7fe1a1a31

Bug 1286530 made TCPSocket ChromeOnly, eliminating both the
dom.mozTCPSocket.enabled preference check as well as the "tcp-socket"
permission check.  The API is now always exposed in chrome contexts.
This patch removes the leftover (and confusing) dead code.

Renamed and why:
- test_tcpsocket_enabled_no_perm.html renamed to
  test_tcpsocket_not_exposed_to_content.html because it's now just a
  question of content never seeing the API.

Removed tests and why:
- test_tcpsocket_enabled_with_perm.html used to be a standalone
  verification of our permission check.  We have no permission check
  now and both test_tcpsocket_jsm.html and
  test_tcpsocket_client_and_server_basics.html serve as tests that we
  affirmatively expose the API and there are no "late" failure (such
  as a secondary check in the parent).

- test_tcpsocket_default_permissions.html duplicated what (now)
  test_tcpsocket_not_exposed_to_content.html accomplishes.  It tried to
  use the API and expect an exception.  This is just superstition in a
  WebIDL.  (TCPSocket was not originally WebIDL-y.)

--HG--
rename : dom/network/tests/test_tcpsocket_enabled_no_perm.html => dom/network/tests/test_tcpsocket_not_exposed_to_content.html
extra : rebase_source : d2231ed3b0fb00541cc266569c2a7908a4074f9c

The use of add_task.js was ever only intended to be temporary until
bug 1078657 landed.

--HG--
extra : rebase_source : d9570859b35691002cf7f4642603f6730ddab7ad

MozReview-Commit-ID: L0FkAGriChD

MozReview-Commit-ID: A8mtz2fJd71

--HG--
extra : rebase_source : 81949d559c5482951ed9186c92d0759dd4a6b3b0

This hint will inform readers if caching is discouraged (e.g., for
SourceBufferResource) or recommmended (e.g., for MediaCache-backed
ChannelMediaResource).

MozReview-Commit-ID: 7hopNS0s5tE

--HG--
extra : rebase_source : 681646cc904229e8513adb148baa085254508049

MozReview-Commit-ID: 3Tjc8ARhZuz

--HG--
extra : rebase_source : 1c8f9a319e9f43866e6e6418619efc89b3250389

MozReview-Commit-ID: 3aUiVU3gKpq

MozReview-Commit-ID: IB8HMmukD1h

--HG--
extra : rebase_source : 7267ae37b0b0d5813ce5510c1aeb225e16649bba

MozReview-Commit-ID: 4CDliBImLR7

MozReview-Commit-ID: KvlrtJlUir8

--HG--
extra : rebase_source : 88b65dfdc34e2df79dec294f3828f1dc6b33ceeb
extra : histedit_source : 42f77c82bd86f54154df52d4fa58c6107771868b

Right now SelectHelper and InputWidgetHelper are loaded in browser.js,
which means they only work for GeckoApp. This patch loads them in
PromptService.js instead, which means they will work in all windows. The
patch also changes some code in SelectHelper and InputWidgetHelper that
used to assume they are running under the browser.xul chrome window.

MozReview-Commit-ID: HveDzIzK1b4

Include the window when using Prompt.jsm in JS so that the prompts can
be directed to the correct Activity.

MozReview-Commit-ID: 7AtYaCJXjDi

MozReview-Commit-ID: HqEyuojy9TG

MozReview-Commit-ID: LyB72VN0tDP

--HG--
extra : rebase_source : 513b95f5da133ac5a515a11ad209723e2237cb24

MozReview-Commit-ID: BVudzxWZnQS

--HG--
extra : rebase_source : ff590dc7e5aa31f6d93baf91f8e8df2f27c95628

MozReview-Commit-ID: Jl48dtpqlm7

--HG--
extra : rebase_source : aa94cd8db6785b19008f67086cd0a9ca3371bcab

MozReview-Commit-ID: ANFE45Ilr7w

--HG--
extra : rebase_source : ccd6b6c4b096975e22f3d9193f43504a97733ed8