Deprecations and removals in Chrome 88

Deprecations and removals in Chrome 88

Chrome 88 beta was released on December 3, 2020 and is expected to become the
stable version in the third week of January 2021.

Don’t allow popups during page unload (enterprises)

Since Chrome 80, pages have no longer been able to open a new page during
unloading using window.open(). Since then enterprises have been able to use
the AllowPopupsDuringPageUnload policy flag to allow popups during page
unload. Starting in Chrome 88, this flag is no longer supported.

Web Components v0 removed

Web Components v0 have been in a reverse origin trial since Chrome 80. This
allowed users of the API time to upgrade their sites while ensuring that new
adopters of Web Components used version 1. The reverse origin trial ends with
Chrome 87, making Chrome 88 the first in which version 0 is no longer supported.
The Web Components v1 APIs replace Web Components v0 and are fully supported in
Chrome, Safari, Firefox, and Edge. This removal covers the items listed below.

Custom Elements v0
HTML Imports
Shadow DOM v0

FTP support removed

Chrome has removed support for FTP
URLs
. The legacy FTP
implementation in Chrome has no support for encrypted connections (FTPS), nor
proxies. Usage of FTP in the browser is sufficiently low that it is no longer
viable to invest in improving the existing FTP client. In addition, more capable
FTP clients are available on all affected platforms.

Google Chrome 72 and later removed support for fetching document subresources
over FTP and rendering of top level FTP resources. Navigating to FTP
URLs results in showing a directory listing or a download depending on the type
of resource. A bug in Google Chrome 74 and later resulted in dropping support
for accessing FTP URLs over HTTP proxies. Proxy support for FTP was removed
entirely in Google Chrome 76.

The remaining capabilities of Google Chrome’s FTP implementation were restricted
to either displaying a directory listing or downloading a resource over
unencrypted connections.

In Chrome 77, FTP support was disabled by default for fifty percent of users but
was available with flags.

In Chrome 88 all FTP support is disabled.

Feedback

Deprecations and removals in Chrome 88

Chrome 88 beta was released on December 3, 2020 and is expected to become the
stable version in the third week of January 2021.

Don't allow popups during page unload (enterprises)

Since Chrome 80, pages have no longer been able to open a new page during
unloading using window.open(). Since then enterprises have been able to use
the AllowPopupsDuringPageUnload policy flag to allow popups during page
unload. Starting in Chrome 88, this flag is no longer supported.

Web Components v0 removed

Web Components v0 have been in a reverse origin trial since Chrome 80. This
allowed users of the API time to upgrade their sites while ensuring that new
adopters of Web Components used version 1. The reverse origin trial ends with
Chrome 87, making Chrome 88 the first in which version 0 is no longer supported.
The Web Components v1 APIs replace Web Components v0 and are fully supported in
Chrome, Safari, Firefox, and Edge. This removal covers the items listed below.

Custom Elements v0
HTML Imports
Shadow DOM v0

FTP support removed

Chrome has removed support for FTP
URLs
. The legacy FTP
implementation in Chrome has no support for encrypted connections (FTPS), nor
proxies. Usage of FTP in the browser is sufficiently low that it is no longer
viable to invest in improving the existing FTP client. In addition, more capable
FTP clients are available on all affected platforms.

Google Chrome 72 and later removed support for fetching document subresources
over FTP and rendering of top level FTP resources. Navigating to FTP
URLs results in showing a directory listing or a download depending on the type
of resource. A bug in Google Chrome 74 and later resulted in dropping support
for accessing FTP URLs over HTTP proxies. Proxy support for FTP was removed
entirely in Google Chrome 76.

The remaining capabilities of Google Chrome’s FTP implementation were restricted
to either displaying a directory listing or downloading a resource over
unencrypted connections.

In Chrome 77, FTP support was disabled by default for fifty percent of users but
was available with flags.

In Chrome 88 all FTP support is disabled.

Feedback


Print Share Comment Cite Upload Translate
APA
| Sciencx (2024-03-29T12:36:25+00:00) » Deprecations and removals in Chrome 88. Retrieved from https://www.scien.cx/2020/12/04/deprecations-and-removals-in-chrome-88/.
MLA
" » Deprecations and removals in Chrome 88." | Sciencx - Friday December 4, 2020, https://www.scien.cx/2020/12/04/deprecations-and-removals-in-chrome-88/
HARVARD
| Sciencx Friday December 4, 2020 » Deprecations and removals in Chrome 88., viewed 2024-03-29T12:36:25+00:00,<https://www.scien.cx/2020/12/04/deprecations-and-removals-in-chrome-88/>
VANCOUVER
| Sciencx - » Deprecations and removals in Chrome 88. [Internet]. [Accessed 2024-03-29T12:36:25+00:00]. Available from: https://www.scien.cx/2020/12/04/deprecations-and-removals-in-chrome-88/
CHICAGO
" » Deprecations and removals in Chrome 88." | Sciencx - Accessed 2024-03-29T12:36:25+00:00. https://www.scien.cx/2020/12/04/deprecations-and-removals-in-chrome-88/
IEEE
" » Deprecations and removals in Chrome 88." | Sciencx [Online]. Available: https://www.scien.cx/2020/12/04/deprecations-and-removals-in-chrome-88/. [Accessed: 2024-03-29T12:36:25+00:00]
rf:citation
» Deprecations and removals in Chrome 88 | | Sciencx | https://www.scien.cx/2020/12/04/deprecations-and-removals-in-chrome-88/ | 2024-03-29T12:36:25+00:00
https://github.com/addpipe/simple-recorderjs-demo