Intent to Deprecate and Remove: navigator.getStorageUpdates()

[Philip Jägenstedt]

Primary eng (and PM) emails

phi...@opera.com

Summary

Remove the getStorageUpdates() method on the Navigator interface, which is a no-op.

Motivation

This is was in the spec between March and August in 2009, between two renames, the first name being navigator.releaseLocks() and the current one is yieldForStorageUpdates():

https://github.com/whatwg/html/commit/8d6e1a82b2f678ae533a6b7b42dbdf2227f6e530

https://github.com/whatwg/html/commit/4bc1015104ff5b441a49856008965ad2a015629f

It was implemented in that short window, a no-op from the beginning:

https://trac.webkit.org/changeset/47397

It's related to the ill-fated storage mutex, so we shouldn't implement yieldForStorageUpdates() either:

https://github.com/whatwg/html/issues/334

Compatibility Risk

Neither Gecko nor IE11 supports getStorageUpdates() or yieldForStorageUpdates(). (I can't test with Edge right now, but assume getStorageUpdates() hasn't been added.)

Alternative implementation suggestion for web developers

Just remove the navigator.getStorageUpdates() call.

Usage information from UseCounter

https://www.chromestatus.com/metrics/feature/timeline/popularity/827

Usage has reached 0.0001% on one day, some days isn't hit at all, and usually rounds to zero.

OWP launch tracking bug

https://crbug.com/465255

Entry on the feature dashboard

https://www.chromestatus.com/features/4780366799831040

Requesting approval to remove too?

Yes, usage is very low, and the removal will be shortly after the branch point to maximize bake time.

[Dimitri Glazkov]

LGTM1

:DG<

[Jochen Eisinger]

lgtm2

[Chris Harrelson]

LGTM3

--
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.