Is UseDraggable really using storage for initial value?

[bergden-resonai]

Describe the bug

I'm trying to follow the example here:

vueuse/packages/core/useDraggable/index.md

Line 39 in cfcc295

For component usage, additional props `storageKey` and `storageType` can be passed to the component and enable the persistence of the element position.

But with storage-type="local" (how can I see the legal values for this type other than session?)

I do see an entry created by the name I passed for storage-key with x,y same as the initial-value, but they're never updated, so upon refresh the element returns to the same place.

Following is a video of the example in the documentation not working:

vuedraggable.mov.mp4

I can't find anything in the code to indicate this should work, but I also couldn't find how the localStorage entry is created to begin with...

Reproduction

https://stackblitz.com/edit/vitejs-vite-4ye5qc/?file=package.json,src%2FApp.vue

System Info

System:
    OS: macOS 13.0.1
    CPU: (8) arm64 Apple M1
    Memory: 76.88 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 18.8.0 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.3.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 108.0.5359.98
    Firefox: 100.0
    Safari: 16.1

Used Package Manager

yarn

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a VueUse issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[wheatjs]

Fixed in #2575