WPT analysis

Open
#86 7 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript

Research direction

Review the listed WPT paths for AbortSignal, Web Crypto API, Console, Streams, compression, encoding, URL, URLPattern, and File API. Investigate streams/transferable/* and the FileReader dependency, then determine whether HTML and area element tests should be split. Done means the WPT coverage gaps and proposed test changes are resolved.

Written by the indexing model from the issue text.

Description

AbortSignal

  • AbortController
  • AbortSignal
+dom/abort/*
-dom/abort/reason-constructor.html

Web Crypto API

  • Crypto
  • CryptoKey
  • SubtleCrypto
  • globalThis.crypto
+WebCryptoAPI/*
-historical.any.*
-algorithm-discards-context.https.window.*

Console

  • globalThis.console
+console/*

Tests are very sparse, and so is spec - it is unclear what side-effects console.log should have across runtimes.

Streams

  • ByteLengthQueuingStrategy
  • CountQueuingStrategy
  • ReadableByteStreamController
  • ReadableStream
  • ReadableStreamBYOBReader
  • ReadableStreamBYOBRequest
  • ReadableStreamDefaultController
  • ReadableStreamDefaultReader
  • TransformStream
  • TransformStreamDefaultController
  • WritableStream
  • WritableStreamDefaultController
  • WritableStreamDefaultWriter
+streams/*
-streams/readable-streams/cross-realm-crash.window.html

streams/transferable/* needs investigation.

(De)compression streams

  • CompressionStream
  • DecompressionStream
+compression/*

Text encoding

  • TextDecoder
  • TextDecoderStream
  • TextEncoder
  • TextEncoderStream
+encoding/*
-encoding/streams/realms.window.html
-encoding/streams/invalid-realm.window.html
-encoding/unsupported-encodings.any.*
-encoding/single-byte-decoder.window.html
-encoding/unsupported-labels.window.html

URL

  • URL
  • URLSearchParams
+url/*
-url/url-setters-a-area.window.html
-url/a-element-origin.html
-url/a-element.html
-url/data-uri-fragment.html
-url/failure.html

Note, a lot of tests in this directory also test using <a> and <area> tags from HTML. It would be good to split those into seperate files.

URLPattern

  • URLPattern
+urlpattern/urlpattern.any.*
+urlpattern/urlpattern-https.any.*
+urlpattern/urlpattern-hasregexpgroups.any.*

File API

  • Blob
  • File
+FileAPI/blob/*
-FileAPI/blob/Blob-constructor-dom.window.html
+FileAPI/file/*
-FileAPI/file/send-file-form-*
+FileAPI/url/url-format.any.*
+FileAPI/url/url-with-fetch.any.*
+FileAPI/unicode.html

A lot of these tests rely on FileReader existing. Should we add this?

Dominant language
Bikeshed
Stars
308
Forks
17
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WinterTC55/proposal-minimum-common-api

All issues in WinterTC55/proposal-minimum-common-api

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.