API Catalog
Visualize and analyze the API overlap between standards specifications and type systems within browsers.
Where is the data from?
Browser information was gathered by traversing the type system within the latest available version of the top browsers. Specification data was gathered by extracting Web IDL definitions from notable web specifications. Note that an API that is shown as detected does not necessarily mean it functions per specification; where the absence of an API under an interface could be due to the browser supporting an API in a different part of the prototype chain. This data is made publicly available to help each browser vendor work toward the goal of a more interoperable web platform.
APIs by interface
Detection statuses
API Name | ![]() | ![]() | ![]() | ![]() | |
---|---|---|---|---|---|
KeyframeEffect | |||||
@@toStringTag | |||||
arguments | |||||
caller | |||||
composite | |||||
constructor | |||||
iterationComposite | |||||
length | |||||
name | |||||
prototype | |||||
setKeyframes | |||||
spacing | |||||
target | |||||
KeyframeEffectReadOnly | |||||
@@toStringTag | |||||
arguments | |||||
caller | |||||
composite | |||||
constructor | |||||
getKeyframes | |||||
iterationComposite | |||||
length | |||||
name | |||||
prototype | |||||
spacing | |||||
target | |||||
SharedKeyframeList | |||||
@@toStringTag | |||||
arguments | |||||
caller | |||||
constructor | |||||
length | |||||
name | |||||
prototype |
No results found