- From: Thomas Steiner <notifications@github.com>
- Date: Tue, 16 Feb 2021 03:00:19 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 16 February 2021 11:00:31 UTC
I played with the Chrome OS implementation and noticed that all storage seems to be shared between all tabs. For example, if an app keeps state in `localStorage`, all tabs share the same state. The Windows 95 implementation you [jokingly linked to](https://github.com/w3c/manifest/issues/737#issue-379994475-permalink:~:text=in%20case%20there%20is%20a%20Windows%2095%20implementation) in the original thread has a dedicated section on [child window data](https://docs.microsoft.com/en-us/windows/win32/winmsg/about-the-multiple-document-interface#child-window-data), which lists two ways of storing data, for example, the name of the current file: - Store child window data in the window structure. - Use window properties. Will there be a platform way to do this, or are implementations expected to store state themselves (and if so, what do you propose to re-identify the same tab)? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/737#issuecomment-779760941
Received on Tuesday, 16 February 2021 11:00:31 UTC