modern-normalize VS standardized-audio-context

Tailwind Preflight is amazing - built on top of modern-normalize, Preflight resets the default inconsistent styles across modern browsers. In addition to modern-normalize, Preflight:

I think this is the same category as https://github.com/sindresorhus/modern-normalize

`modern-normalized.css` can be for MVP too. Honestly few < 100 lines on top of normalized one isn't that much work.

You should inspect the elements to find out where the margins around the nav bar are coming from. I assume you never zeroed the margins on the body, but it's good practice to inspect your properties to find out for yourself where things are coming from. To fix, you can probably add body {margin: 0;} to your CSS. An even better way would be to load a modern reset before your styles, something like modern normalize.

Tailwind CSS comes with "an opinionated set of base styles" called Preflight. A helpful CSS reset built on top of modern-normalize.

You know this exists right ?

I recently switched from normalize.css to a "modern" fork https://github.com/sindresorhus/modern-normalize

Just tested it with standardized-audio-context and it doesn't implement this missing functionality unfortunately

Potentially a repo that might come in handy: - https://github.com/chrisguttandin/standardized-audio-context/. This lib aims to standardize Web Audio API behavior across browsers, as not all browser support is the same. I have found it quite handy.

There are amazing projects like this that attempt to standardize Web APIs, but now you have to includes this ~3mb (before minification/compression) library into your web app