Store the current SequenceManagerImpl instance in TLS

Now that the backend for MessageLoop is always a SequenceManager it no
longer makes sense to have the TLS logic in MessageLoopCurrent.

Eventually MessageLoopBase will disappear completely and
MessageLoopCurrent will use the API exposed by SequenceManager. This
patch is a step in that direction.

Bug: 891670
Change-Id: I24a76ded54fcf4b95bc8192ce0fe413aaeee162d
Commit-Queue: Carlos Caballero <>
Reviewed-by: Sami Kyöstilä <>
Reviewed-by: Gabriel Charette <>
Reviewed-by: Alexander Timin <>
Cr-Commit-Position: refs/heads/master@{#641834}
4 files changed