brgol...@google.com, m...@chromium.com, jadek...@chromium.com
Storage partitioning explainer
We propose to remove support for loading media via filesystem:// URLs on Android.
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.
None
None
N/A
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.
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.
Developers can continue to load media from other schemes (http, https, blob, file, etc.).
Android Chrome (Browser App): 0.0000001%
Android Webview: 0.0%
https://bugs.chromium.org/p/chromium/issues/detail?id=1258029
--
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+...@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.
How confident can we be in the WebView counter? I'd expect this to be used more in WebView than on other platforms.
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_cAggyuYtcNrNrQKT4vEL5iRSp6qMoOEJ8cFvaq6iSpg%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@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.
--
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+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@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.
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_cAggyuYtcNrNrQKT4vEL5iRSp6qMoOEJ8cFvaq6iSpg%40mail.gmail.com.
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/1f198100-936d-41e3-8952-826c9bb0b9ban%40chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAP_mGKrEhMzfwrzz1DqaCusAcErOiMA3G0X8ufE%3DNNdJtqWg_A%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@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.
--
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+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@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.
--
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+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@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.
--
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+...@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@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.
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALDP-vQNK58p5zxkcaLH554OWRxJCtOoUrUS97HHema2_XG8Wg%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8670f31d-d4d2-443f-8757-250bb5611cdbn%40chromium.org.
-- Frédéric Wang
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEdON6acwSf5c2uJ7ZWgJa32q7tnj%2B%2Bcobqc5Mw3ksu2pFUHXg%40mail.gmail.com.
Hey all, following up with a proposed plan for moving forward here -
The Chrome Storage team considers the old Filesystem API to be an undesirable API, one that should eventually be deprecated and removed. Our short-term goal is to partition storage APIs, but Android media playback from filesystem:// URLs is the one codepath where this is not easily done. Given it’s near-zero usage, we’d like to remove it instead. However, it is a bit awkward to only remove this one use case on this one platform, especially since we want to eventually remove it everywhere. So, in order to meet both our short-term needs and the Storage team’s long-term goals we propose the following:
Remove support for media playback from filesystem:// URLs on Chrome on Android (the original proposal in this thread).
Remove support for media playback from filesystem:// across all platforms.
Eventually, remove support for filesystem://.
In order to get to steps 2 and 3 we need to:
Formally deprecate filesystem://, sending devtools Issues and deprecation reports. We’ll work on I2Ds for both 2 and 3 with detailed timelines (as they emerge).
Add an Enterprise policy to allow more time for migration, and possibly a deprecation trial as well
Work with DevRel to write an article recommending workarounds and a migration path
Work with internal and external partners to ensure we can drive down usage to a level where we’re comfortable removing filesystem://. We’ll focus efforts on ChromeOS media playback first.
Investigate adding capabilities to the platform that addresses the use cases of media playback from Cache storage without requiring a ServiceWorker
LGTM3 to remove filesystem:// on Android only for now.
For whoever files the deprecation for the other platforms, I want to second what Yoav said about deprecations needing a time limit. Deprecations without time limits are not effective and we avoid those.
/Daniel
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/1030809b-8016-48f9-90bb-fde5891890aen%40chromium.org.