Scott Haseley shaseley

## react-scheduler-test.html
<!DOCTYPE html>
<meta charset="utf-8">
<title>Test React Scheduler</title>

<script src="rs.js"></script>

<button onclick="runTest()">Run test</button>

<script>
const TEST_DURATION = 300000;

## abortsignal-any-poc.js
<script>

let abortProto = AbortController.prototype;
let oldAbort = AbortController.prototype.abort;

Object.assign(abortProto, {
  abort(reason) {
    oldAbort.call(this, reason);
    if (this.signal.__dependents) {
      for (let controller of this.signal.__dependents) {

## extending-abort-signal.md

      
        
          
            
              
              1 file
            
          
          
            
              
              0 forks
            
          
          
            
              
              0 comments
            
          
          
            
              
              0 stars
            
          
        
        
          
              
          
          
            
                shaseley
                / extending-abort-signal.md
            
            
              Created
              March 27, 2020 20:42
            
          
        
      
        
  
      
    Supporting Multiple Signals on the Web Platform

Introduction

The signal/controller pattern was introduced as the way to control ongoing
async work, initially for
cancellation via
AbortController
and
AbortSignal.
	<!DOCTYPE html>
	<meta charset="utf-8">
	<title>Test React Scheduler</title>

	<script src="rs.js"></script>

	<button onclick="runTest()">Run test</button>

	<script>
	const TEST_DURATION = 300000;
	<script>

	let abortProto = AbortController.prototype;
	let oldAbort = AbortController.prototype.abort;

	Object.assign(abortProto, {
	abort(reason) {
	oldAbort.call(this, reason);
	if (this.signal.__dependents) {
	for (let controller of this.signal.__dependents) {