Automated analysis of in parallel algorithms

[tidoust]

This is the result of running the in parallel algorithm analysis on a crawl result with algorithm extracts: see https://github.com/w3c/reffy/pull/1614 and https://github.com/w3c/strudy/pull/645.

As explained in Strudy's PR, the list includes all problems that had been identified in #1 (but 2). It also includes problems that had been missed.

• Accelerated Shape Detection in Images
  • The BarcodeDetector/getSupportedFormats() algorithm has a parallel step that resolves/rejects a promise directly
• Audio Output Devices API
  • The HTMLMediaElement/setSinkId() algorithm has a parallel step that resolves/rejects a promise directly
  • The MediaDevices/selectAudioOutput() algorithm has a parallel step that resolves/rejects a promise directly
• Background Fetch
  • The create record objects algorithm has a parallel step that resolves/rejects a promise directly
  • The get(id) algorithm has a parallel step that resolves/rejects a promise directly
  • The getIds() algorithm has a parallel step that resolves/rejects a promise directly
  • The abort() algorithm has a parallel step that resolves/rejects a promise directly
  • The updateUI(options) algorithm has a parallel step that resolves/rejects a promise directly
• Contact Picker API
  • The getProperties() algorithm has a parallel step that resolves/rejects a promise directly
• Content Index
  • The add(description) algorithm has a parallel step that resolves/rejects a promise directly
  • The delete(id) algorithm has a parallel step that resolves/rejects a promise directly
  • The getAll() algorithm has a parallel step that resolves/rejects a promise directly
• Cookie Store API
  • The get(name) algorithm has a parallel step that resolves/rejects a promise directly
  • The get(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The getAll(name) algorithm has a parallel step that resolves/rejects a promise directly
  • The getAll(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The set(name, value) algorithm has a parallel step that resolves/rejects a promise directly
  • The set(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The delete(name) algorithm has a parallel step that resolves/rejects a promise directly
  • The delete(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The subscribe(subscriptions) algorithm has a parallel step that resolves/rejects a promise directly
  • The getSubscriptions() algorithm has a parallel step that resolves/rejects a promise directly
  • The unsubscribe(subscriptions) algorithm has a parallel step that resolves/rejects a promise directly
• Credential Management Level 1
  • The Request a Credential algorithm has a parallel step that resolves/rejects a promise directly
  • The Create a Credential algorithm has a parallel step that resolves/rejects a promise directly
  • The Prevent Silent Access algorithm has a parallel step that resolves/rejects a promise directly
• CSS Object Model (CSSOM)
  • The CSSStyleSheet/replace(text) algorithm has a parallel step that resolves/rejects a promise directly
• Element Capture
  • The BrowserCaptureMediaStreamTrack/restrictTo() algorithm has a parallel step that resolves/rejects a promise directly
• Encrypted Media Extensions
  • The Navigator/requestMediaKeySystemAccess() algorithm has a parallel step that resolves/rejects a promise directly
  • The MediaKeySystemAccess/createMediaKeys() algorithm has a parallel step that resolves/rejects a promise directly
  • The MediaKeys/setServerCertificate() algorithm has a parallel step that resolves/rejects a promise directly
  • The MediaKeySession/generateRequest() algorithm has a parallel step that resolves/rejects a promise directly
  • The MediaKeySession/load() algorithm has a parallel step that resolves/rejects a promise directly
  • The MediaKeySession/update() algorithm has a parallel step that resolves/rejects a promise directly
  • The HTMLMediaElement/setMediaKeys() algorithm has a parallel step that resolves/rejects a promise directly
• EyeDropper API
  • The EyeDropper/open() algorithm has a parallel step that resolves/rejects a promise directly
• Federated Credential Management API
  • The attempt to disconnect algorithm has a parallel step that resolves/rejects a promise directly
  • The getUserInfo algorithm has a parallel step that resolves/rejects a promise directly
• File System Access
  • The queryPermission(descriptor) algorithm has a parallel step that resolves/rejects a promise directly
  • The requestPermission(descriptor) algorithm has a parallel step that resolves/rejects a promise directly
  • The showOpenFilePicker(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The showSaveFilePicker(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The showDirectoryPicker(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The getAsFileSystemHandle() algorithm has a parallel step that resolves/rejects a promise directly
• Fullscreen API Standard
  • The requestFullscreen(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The exit fullscreen algorithm has a parallel step that resolves/rejects a promise directly
• Gamepad
  • The GamepadHapticActuator/reset() algorithm has a parallel step that resolves/rejects a promise directly
• Geolocation Sensor
  • The read algorithm has a parallel step that resolves/rejects a promise directly
• Get Installed Related Apps API
  • The getInstalledRelatedApps() algorithm has a parallel step that resolves/rejects a promise directly
• Handwriting Recognition API
  • The navigator-query-handwriting-recognizer algorithm has a parallel step that resolves/rejects a promise directly
  • The navigator-create-handwriting-recognizer algorithm has a parallel step that resolves/rejects a promise directly
  • The handwriting-drawing-get-prediction algorithm has a parallel step that resolves/rejects a promise directly
• HTML Standard
  • The HTMLImageElement/decode() algorithm has a parallel step that resolves/rejects a promise directly
  • The algorithm that starts with "A window event loop eventLoop must also run the following in parallel, as long as it exists:" has a parallel step that fires an event directly
  • The WindowOrWorkerGlobalScope/createImageBitmap(image, options) algorithm has a parallel step that resolves/rejects a promise directly
• Idle Detection API
  • The requestPermission() algorithm has a parallel step that resolves/rejects a promise directly
• Indexed Database API 3.0
  • The databases() algorithm has a parallel step that resolves/rejects a promise directly
• JS Self-Profiling API
  • The algorithm that starts with "Stops the profiler and returns a trace. This method MUST run these steps:" has a parallel step that resolves/rejects a promise directly
• Keyboard Map
  • The keyboard-getlayoutmap algorithm has a parallel step that resolves/rejects a promise directly
• Local Font Access
  • The queryLocalFonts(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The blob() algorithm has a parallel step that resolves/rejects a promise directly
• Managed Configuration API
  • The NavigatorManagedData/getManagedConfiguration(keys) algorithm has a parallel step that resolves/rejects a promise directly
• Media Capabilities
  • The algorithm that starts with "The decodingInfo() method method MUST run the following steps:" has a parallel step that resolves/rejects a promise directly
  • The algorithm that starts with "The encodingInfo() method MUST run the following steps:" has a parallel step that resolves/rejects a promise directly
• Media Capture and Streams
  • The MediaDevices/enumerateDevices() algorithm has a parallel step that resolves/rejects a promise directly
  • The MediaDevices/getUserMedia() algorithm has a parallel step that resolves/rejects a promise directly
• Media Session
  • The update capture state algorithm algorithm has a parallel step that resolves/rejects a promise directly
• MediaStream Image Capture
  • The ImageCapture/takePhoto(photoSettings) algorithm has a parallel step that resolves/rejects a promise directly
  • The ImageCapture/getPhotoCapabilities() algorithm has a parallel step that resolves/rejects a promise directly
  • The ImageCapture/getPhotoSettings() algorithm has a parallel step that resolves/rejects a promise directly
  • The ImageCapture/grabFrame() algorithm has a parallel step that resolves/rejects a promise directly
• Payment Handler API
  • The algorithm that starts with "Upon receiving a PaymentRequest by way of PaymentRequest.show() and subsequent user selection of a payment handler, the user agent MUST run the following steps:" has a parallel step that resolves/rejects a promise directly
  • An algorithm has a parallel step that resolves/rejects a promise directly
• Payment Request API 1.1
  • The algorithm that starts with "The show(optional detailsPromise) method MUST act as follows:" has a parallel step that resolves/rejects a promise directly
  • The algorithm that starts with "The complete() method MUST act as follows:" has a parallel step that resolves/rejects a promise directly
  • The can make payment algorithm algorithm has a parallel step that resolves/rejects a promise directly
• Picture-in-Picture
  • The algorithm that starts with "The requestPictureInPicture() method, when invoked, MUST return a new promise promise and run the following steps in parallel:" has a parallel step that resolves/rejects a promise directly
  • The algorithm that starts with "The exitPictureInPicture() method, when invoked, MUST return a new promise promise and run the following steps in parallel:" has a parallel step that resolves/rejects a promise directly
• Presentation API
  • The PresentationRequest/start() algorithm has a parallel step that resolves/rejects a promise directly
  • The PresentationRequest/reconnect() algorithm has a parallel step that resolves/rejects a promise directly
  • The PresentationRequest/getAvailability() algorithm has a parallel step that resolves/rejects a promise directly
  • The monitoring incoming presentation connections algorithm has a parallel step that resolves/rejects a promise directly
• Region Capture
  • The BrowserCaptureMediaStreamTrack/cropTo() algorithm has a parallel step that resolves/rejects a promise directly
• Remote Playback API
  • The RemotePlayback/prompt() algorithm has a parallel step that resolves/rejects a promise directly
• Screen Capture
  • The MediaDevices/getDisplayMedia() algorithm has a parallel step that resolves/rejects a promise directly
• Screen Orientation
  • The apply orientation lock algorithm has a parallel step that resolves/rejects a promise directly
• Service Workers
  • The navigator-service-worker-getRegistration algorithm has a parallel step that resolves/rejects a promise directly
  • The navigation-preload-manager-enable algorithm has a parallel step that resolves/rejects a promise directly
  • The navigation-preload-manager-disable algorithm has a parallel step that resolves/rejects a promise directly
  • The navigation-preload-manager-setheadervalue algorithm has a parallel step that resolves/rejects a promise directly
  • The navigation-preload-manager-getstate algorithm has a parallel step that resolves/rejects a promise directly
  • The service-worker-global-scope-skipwaiting algorithm has a parallel step that resolves/rejects a promise directly
  • The client-postmessage-options algorithm has a parallel step that fires an event directly
  • The clients-get algorithm has a parallel step that resolves/rejects a promise directly
  • The clients-claim algorithm has a parallel step that resolves/rejects a promise directly
  • The cache-match algorithm has a parallel step that resolves/rejects a promise directly
  • The cache-matchall algorithm has a parallel step that resolves/rejects a promise directly
  • The cache-storage-match algorithm has a parallel step that resolves/rejects a promise directly
  • The cache-storage-has algorithm has a parallel step that resolves/rejects a promise directly
  • The cache-storage-open algorithm has a parallel step that resolves/rejects a promise directly
  • The cache-storage-delete algorithm has a parallel step that resolves/rejects a promise directly
  • The cache-storage-keys algorithm has a parallel step that resolves/rejects a promise directly
  • The Handle Fetch algorithm has a parallel step that resolves/rejects a promise directly
• Test Utils Standard
  • The algorithm that starts with "The gc() method must run these steps:" has a parallel step that resolves/rejects a promise directly
• The Capture-Handle Actions Mechanism
  • The MediaStreamTrack/sendCaptureAction() algorithm has a parallel step that resolves/rejects a promise directly
• Viewport Capture
  • The MediaDevices/getViewportMedia() algorithm has a parallel step that resolves/rejects a promise directly
• VirtualKeyboard API
  • The VirtualKeyboard/show() algorithm has a parallel step that fires an event directly
  • The VirtualKeyboard/hide() algorithm has a parallel step that fires an event directly
• Web Background Synchronization
  • The SyncManager/register(tag) algorithm has a parallel step that resolves/rejects a promise directly
  • The SyncManager/getTags() algorithm has a parallel step that resolves/rejects a promise directly
  • The fire a sync event algorithm has a parallel step that fires an event directly
• Web Bluetooth
  • The getDevice invocation algorithm has a parallel step that resolves/rejects a promise directly
  • The requestDevice invocation algorithm has a parallel step that resolves/rejects a promise directly
  • The query Bluetooth cache algorithm has a parallel step that resolves/rejects a promise directly
  • The BluetoothRemoteGATTServer connect algorithm has a parallel step that resolves/rejects a promise directly
  • The BluetoothRemoteGATTService construction algorithm has a parallel step that resolves/rejects a promise directly
  • The BluetoothRemoteGATTCharacteristic constructor algorithm has a parallel step that resolves/rejects a promise directly
  • The BluetoothRemoteGATTCharacteristic readValue() algorithm has a parallel step that resolves/rejects a promise directly
  • The Write Characteristic value algorithm has a parallel step that resolves/rejects a promise directly
  • The BluetoothRemoteGATTCharacteristic startNotifications algorithm has a parallel step that resolves/rejects a promise directly
  • The BluetoothCharacteristicProperties constructor algorithm has a parallel step that resolves/rejects a promise directly
  • The BluetoothRemoteGATTDescriptor constructor algorithm has a parallel step that resolves/rejects a promise directly
  • The BluetoothRemoteGATTDescriptor readValue algorithm has a parallel step that resolves/rejects a promise directly
  • The BluetoothRemoteGATTDescriptor writeValue algorithm has a parallel step that resolves/rejects a promise directly
• Web Bluetooth Scanning
  • The requestLEScan(options) algorithm has a parallel step that resolves/rejects a promise directly
• Web Cryptography API
  • The SubtleCrypto/encrypt() algorithm has a parallel step that resolves/rejects a promise directly
  • The SubtleCrypto/sign() algorithm has a parallel step that resolves/rejects a promise directly
  • The SubtleCrypto/digest() algorithm has a parallel step that resolves/rejects a promise directly
  • The SubtleCrypto/generateKey() algorithm has a parallel step that resolves/rejects a promise directly
  • The SubtleCrypto/deriveKey() algorithm has a parallel step that resolves/rejects a promise directly
  • The SubtleCrypto/deriveBits() algorithm has a parallel step that resolves/rejects a promise directly
  • The SubtleCrypto/importKey() algorithm has a parallel step that resolves/rejects a promise directly
  • The SubtleCrypto/exportKey() algorithm has a parallel step that resolves/rejects a promise directly
  • The SubtleCrypto/wrapKey() algorithm has a parallel step that resolves/rejects a promise directly
  • The SubtleCrypto/unwrapKey() algorithm has a parallel step that resolves/rejects a promise directly
• Web NFC API
  • The NDEFReader/write() algorithm has a parallel step that resolves/rejects a promise directly
  • The NDEFReader/makeReadOnly() algorithm has a parallel step that resolves/rejects a promise directly
  • The clean up the pending scan algorithm has a parallel step that resolves/rejects a promise directly
• Web Periodic Background Synchronization
  • The Process periodic sync registrations algorithm has a parallel step that fires an event directly
• WebCodecs
  • The ImageDecoder/isTypeSupported(type) algorithm has a parallel step that resolves/rejects a promise directly
• WebDriver
  • The algorithm that starts with "The remote end steps, given session, URL variables and parameters are:" has a parallel step that resolves/rejects a promise directly
  • The algorithm that starts with "The remote end steps, given session, URL variables and parameters are:" has a parallel step that resolves/rejects a promise directly
• WebHID API
  • The algorithm that starts with "The forget() method steps are:" has a parallel step that resolves/rejects a promise directly
• WebRTC Encoded Transform
  • The algorithm that starts with "The SFrame transform algorithm, given sframe as a SFrameTransform object and frame, runs these steps:" has a parallel step that resolves/rejects a promise directly
  • The generate key frame algorithm algorithm has a parallel step that resolves/rejects a promise directly
  • The send request key frame algorithm algorithm has a parallel step that resolves/rejects a promise directly
• WebRTC: Real-Time Communication in Browsers
  • The RTCPeerConnection/generateCertificate() algorithm has a parallel step that resolves/rejects a promise directly
  • The RTCRtpSender/replaceTrack() algorithm has a parallel step that resolves/rejects a promise directly
  • The RTCRtpSender/getStats() algorithm has a parallel step that resolves/rejects a promise directly
  • The RTCRtpReceiver/getStats() algorithm has a parallel step that resolves/rejects a promise directly
  • The RTCPeerConnection/getStats() algorithm has a parallel step that resolves/rejects a promise directly
• WebTransport
  • The WebTransport/getStats() algorithm has a parallel step that resolves/rejects a promise directly
  • The WebTransport/createBidirectionalStream(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The WebTransport/createUnidirectionalStream(options) algorithm has a parallel step that resolves/rejects a promise directly
  • The pull bytes algorithm has a parallel step that resolves/rejects a promise directly
  • The cancel algorithm has a parallel step that resolves/rejects a promise directly
• WebUSB API
  • The algorithm that starts with "The getDevices() method, when invoked, MUST return a new Promise and run the following steps in parallel:" has a parallel step that resolves/rejects a promise directly
  • The request the "usb" permission algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.open() algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.close() algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.forget() algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.selectConfiguration(configurationValue) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.claimInterface(interfaceNumber) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.releaseInterface(interfaceNumber) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.selectAlternateInterface(interfaceNumber, alternateSetting) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.controlTransferIn(setup, length) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.controlTransferOut(setup, data) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.clearHalt(direction, endpointNumber) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.transferIn(endpointNumber, length) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.transferOut(endpointNumber, data) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.isochronousTransferIn(endpointNumber, packetLengths) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.isochronousTransferOut(endpointNumber, data, packetLengths) algorithm has a parallel step that resolves/rejects a promise directly
  • The USBDevice.reset() algorithm has a parallel step that resolves/rejects a promise directly
• WebXR Device API
  • The session-supported algorithm has a parallel step that resolves/rejects a promise directly
  • The request-reference-space algorithm has a parallel step that resolves/rejects a promise directly

[dontcallmedom]

Already fabulous results above! can you share somewhere the JSON generated by reffy?

[tidoust]

Already fabulous results above! can you share somewhere the JSON generated by reffy?

Sure! I put the results of the crawl under the data folder in this repository.

[dontcallmedom]

any chance you could update crawl results with the latest reffy code (before it reaches webref)?

[tidoust]

Done. (FWIW, I plan to fix curation in Webref before I deploy the new version of Reffy. Just to err on the sane side)

[tidoust]

For info, algorithms extracts have now reached the main and curated branch of Webref. I will no longer update the data in this repository as a result.