Additionally to follow up on @Chris Harrelson <chris...@chromium.org>'s question on usage - Chrome OS usage is 1.38%, Mac OSX is at 0.12% and Windows is 0.05%. We propose to only remove support for Android here.
On Tue, Jan 25, 2022 at 7:13 PM Chris Harrelson <chris...@chromium.org> wrote: > Hi, could you outline the use counter values for other platforms? Also, is > there something special about Android that leads you to want to disable > only there? > > On Tue, Jan 25, 2022 at 1:58 PM Brianna Goldstein < > brgoldst...@chromium.org> wrote: > >> Primary eng (and PM) emails >> >> brgoldst...@google.com, m...@chromium.com <m...@google.com>, >> jadekess...@chromium.com >> >> Explainer >> >> Storage partitioning explainer >> <https://github.com/wanderview/quota-storage-partitioning/blob/main/explainer.md#storage-apis> >> >> Summary >> >> We propose to remove support for loading media via filesystem:// URLs on >> Android. >> >> >> Motivation >> >> As part of our storage partitioning efforts, we will need to update >> Filesystem URLs to be partitioned by StorageKey rather than by Origin. >> Doing this will add complexity since the entire current codepath on Android >> is not dependent on Blink where StorageKey currently lives. On Android only >> 0.0000001% of URLs loaded by <audio> or <video> use the filesystem:// URL >> scheme and we consider this low enough usage to remove support, rather than >> do the work of partitioning. Note that this removal is only for Android. On >> other platforms there will be no effect and media playback of filesystem:// >> URLs will continue to work. >> >> Blink component >> >> Blink>Storage >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EStorage> >> >> Initial public proposal >> >> None >> >> TAG review >> >> None >> >> TAG review status >> >> N/A >> >> Interoperability and Compatibility RiskInteroperability risk: >> >> The filesystem:// URL scheme was never widely adopted and is only >> implemented by Chrome. Therefore there should be no interoperability risks >> associated with this feature depreciation. >> >> Compatibility risk: >> >> This feature is very low usage as only 0.0000001% of URLs loaded by >> <audio> or <video> use the filesystem:// URL scheme. Therefore the expected >> compatibility risk is very low. >> >> Alternative implementation suggestion for web developers >> >> Developers can continue to load media from other schemes (http, https, >> blob, file, etc.). >> >> Usage information from UMA >> >> Android Chrome (Browser App): 0.0000001% >> >> Android Webview: 0.0% >> >> Tracking Bug >> >> https://bugs.chromium.org/p/chromium/issues/detail?id=1258029 >> >> Entry on the feature dashboard >> >> https://chromestatus.com/feature/5632429577469952 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to blink-dev+unsubscr...@chromium.org. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALDP-vS2KA47PGLh3YkxqAr9z24nP1_u%2BtvY6eWzqSQgq987cQ%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALDP-vS2KA47PGLh3YkxqAr9z24nP1_u%2BtvY6eWzqSQgq987cQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALDP-vTTm8-jZtpK7BhhJKSmu_WxLr6svR%2B9gvRhRC_AdJqxWw%40mail.gmail.com.
