SequencedTaskRunner seems to provide the mutual exclusion properties necessary for mojo bindings. Supporting this would allow mojo bindings to live on a blocking pool sequence. See issue 676960 for an example where that would be useful.
Implementation-wise, this gets a bit complicated if we want to support sync IPCs to/from a sequence, since it would require sequence-local storage for SyncHandleRegistry. Also missing is an equivalent to MessageLoop::DestructionObserver.
Comment 1 by dcheng@chromium.org
, Jan 4 2017Components: Internals>TaskScheduler