From 09aac34e58549698930735bdd10685b9ee54a9ac Mon Sep 17 00:00:00 2001 From: vyv03354 Date: Tue, 27 May 2014 20:47:30 -0700 Subject: [PATCH] PDF.js no longer depends on TextDecoder --- Required-Browser-Features.md | 50 ------------------------------------ 1 file changed, 50 deletions(-) diff --git a/Required-Browser-Features.md b/Required-Browser-Features.md index a6dcead..daa41a9 100644 --- a/Required-Browser-Features.md +++ b/Required-Browser-Features.md @@ -657,31 +657,6 @@ if the browser cannot tell if fonts are loaded and can be used. -## TextDecoder is supported - -Some East Asian PDFs will be completely garbled, if the browser does not support the `TextDecoder`. See http://encoding.spec.whatwg.org/ - - - - - - - - - - - - - - - - - - - - -
ChromeFirefox (Gecko)Internet ExplorerOperaSafari
No (v.24)Yes (v.18)No (v.10)?No (v.6)
- ## Worker is supported/enabled The PDF.js will execute all code (even long running) on the main thread, @@ -785,28 +760,3 @@ if the browser cannot request network binary data from web workers. - -## TextDecoder is supported in web workers - -Texts will not be copied properly on some East Asian PDFs. If the browser does not support the `TextDecoder` in web workers, the `FileReaderSync` will be used instead. - - - - - - - - - - - - - - - - - - - - -
ChromeFirefox (Gecko)Internet ExplorerOperaSafari
Emulated (v.24)Yes (v.20)Emulated (v.10)?No (v.6)