From 9fcb8e1aa678af3158a5960c558343f549f8e3e5 Mon Sep 17 00:00:00 2001 From: Hamir Mahal Date: Sat, 6 Mar 2021 13:39:29 -0800 Subject: [PATCH] change "full" to "filling" to increase readability --- files/en-us/web/api/web_audio_api/best_practices/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/web_audio_api/best_practices/index.html b/files/en-us/web/api/web_audio_api/best_practices/index.html index c2d2da4e1977f84..784b3f1f3cfdaa4 100644 --- a/files/en-us/web/api/web_audio_api/best_practices/index.html +++ b/files/en-us/web/api/web_audio_api/best_practices/index.html @@ -29,7 +29,7 @@

Cross browser & legacy support

The Web Audio API specification is constantly evolving and like most things on the web, there are some issues with it working consistently across browsers. Here we'll look at options for getting around cross-browser problems.

-

There's the standardised-audio-context npm package, which creates API functionality consistently across browsers, full holes as they are found. It's constantly in development and endeavours to keep up with the current specification.

+

There's the standardised-audio-context npm package, which creates API functionality consistently across browsers, filling holes as they are found. It's constantly in development and endeavours to keep up with the current specification.

There is also the option of libraries, of which there are a few depending on your use case. For a good all-rounder, howler.js is a good choice. It has cross-browser support and, provides a useful subset of functionality. Although it doesn't harness the full gamut of filters and other effects the Web Audio API comes with, you can do most of what you'd want to do.