diff --git a/native_client_sdk/doc_generated/migration/index.html b/native_client_sdk/doc_generated/migration/index.html index df685dbef25f9c..18a7eff80e5607 100644 --- a/native_client_sdk/doc_generated/migration/index.html +++ b/native_client_sdk/doc_generated/migration/index.html @@ -5,10 +5,21 @@

(P)NaCl Deprecation Announcements

Given the momentum of cross-browser WebAssembly support, we plan to focus our native code efforts on WebAssembly going forward and plan to remove support for -PNaCl in Q2 2019 (except for Chrome Apps). We believe that the vibrant +PNaCl in Q4 2019 (except for Chrome Apps). We believe that the vibrant ecosystem around WebAssembly makes it a better fit for new and existing high-performance web apps and that usage of PNaCl is sufficiently low to warrant deprecation.

+

As of Chrome 76, PNaCl on the open web has been moved behind an +Origin Trial +which is a mechanism for web developers to register and get access to a feature that isn’t on by default. +This is usually a new proposed feature but in this case it’s a feature being deprecated. +A developer can register on the Origin Trial Console +and receive a token, which can be embedded into a page and will enable the feature without the user needing to use a flag. +(For more details see the linked guide). The trial is scheduled to last through Chrome 78, approximately until December 2019. +This change is not intended to affect NaCl or PNaCl in Chrome Apps or extensions, and the "enable-nacl" +flag in chrome://flags can also be used to enable PNaCl locally for testing +(this flag also retains its current function of enabling non-PNaCl "native" NaCl on any page). +

We also recently announced the deprecation Q1 2018 of Chrome Apps outside of ChromeOS.

diff --git a/native_client_sdk/src/doc/migration/index.rst b/native_client_sdk/src/doc/migration/index.rst index 7f61dc5a511bc6..6b43259ad59d9d 100644 --- a/native_client_sdk/src/doc/migration/index.rst +++ b/native_client_sdk/src/doc/migration/index.rst @@ -8,11 +8,24 @@ WebAssembly Migration Guide Given the momentum of cross-browser WebAssembly support, we plan to focus our native code efforts on WebAssembly going forward and plan to remove support for -PNaCl in Q2 2019 (except for Chrome Apps). We believe that the vibrant +PNaCl in Q4 2019 (except for Chrome Apps). We believe that the vibrant ecosystem around `WebAssembly `_ makes it a better fit for new and existing high-performance web apps and that usage of PNaCl is sufficiently low to warrant deprecation. +As of Chrome 76, PNaCl on the open web has been moved behind an +`Origin Trial +`_, +which is a mechanism for web developers to register and get access to a feature that isn't on by default. +This is usually a new proposed feature but in this case it's a feature being deprecated. +A developer can register on the `Origin Trial Console +`_ +and receive a token, which can be embedded into a page and will enable the feature without the user needing to use a flag. +(For more details see the linked guide). The trial is scheduled to last through Chrome 78, approximately until December 2019. +This change is not intended to affect NaCl or PNaCl in Chrome Apps or extensions, and the "enable-nacl" +flag in chrome://flags can also be used to enable PNaCl locally for testing +(this flag also retains its current function of enabling non-PNaCl "native" NaCl on any page). + We also recently announced the deprecation Q1 2018 of `Chrome Apps `_