Skip to content

docs: fix typo and grammar in browser-support #2515

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 1, 2021
Merged

docs: fix typo and grammar in browser-support #2515

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions guide/src/reference/browser-support.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,10 @@ also like to be aware of it!
that at this time no bundler will do this by default, but we'd love to
document plugins which do this if you are aware of one!

* **Edge before 79+** - the `TextEncoder` and `TextDecoder` APIs where not
available in Edge which `wasm-bindgen` uses to encode/decode strings between
JS and Rust. You can polyfill this with at least one of two strategies:
* **Edge before 79+** - the `TextEncoder` and `TextDecoder` APIs, which
`wasm-bindgen` uses to encode/decode strings between JS and Rust, were not
available before version 79. You can polyfill this with at least one of two
strategies:

1. If using a bundler, you can likely configure the bundler to polyfill these
types by default. For example if you're using Webpack you can use the
Expand Down