MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Moving from WebView to WebView2 and handling localStorage/IndexedDB data.
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Realise this is probably too soon and assumes a lot but figured I'd list the scenario.
I've got a scenario where I've got a deployed UWP/appx for my PWA in the store using the current WebView that's using localStorage and IndexedDB. Would this storage be able to be preserved or accessible somehow when moving to WebView2? I can see a scenario that might appear where I might "lose" data.
- User is offline and enters some data.
- User terminates application.
- User device comes online.
- Application is updated from app store.
- User opens application.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named. Start by reviewing the WebView-to-WebView2 migration scenario and the linked AB#27374585 work item, focusing on localStorage and IndexedDB across the stated offline, termination, update, and reopen sequence. Done means documenting whether the data remains preserved or accessible and what migration behavior is supported.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100