Bug 1757372 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
All the communication which is required for clearing sessionStorage data in the main process and content processes is now done using `StorageObserver`, `StorageObserverSink` and `PSessionStorageObserver`. There's only one IPC message:
```
Observe(nsCString topic,
                nsString originAttributesPattern,
                nsCString originScope
```

This is not very flexible as we found out in bug 1688665. It would be better to have a dedicated service with individual methods for specific clearing scenarios. This bug is about adding basic infrastructure for that using latest patterns for services like this.
Revision 1 by
on 
All the communication which is required for clearing sessionStorage data in the main process and content processes is now done using `StorageObserver`, `StorageObserverSink` and `PSessionStorageObserver`. There's only one IPC message:
```
Observe(nsCString topic,
        nsString originAttributesPattern,
                nsCString originScope
```

This is not very flexible as we found out in bug 1688665. It would be better to have a dedicated service with individual methods for specific clearing scenarios. This bug is about adding basic infrastructure for that using latest patterns for services like this.
Revision 2 by
on 
All the communication which is required for clearing sessionStorage data in the main process and content processes is now done using `StorageObserver`, `StorageObserverSink` and `PSessionStorageObserver`. There's only one IPC message:
```
Observe(nsCString topic,
        nsString originAttributesPattern,
        nsCString originScope
```

This is not very flexible as we found out in bug 1688665. It would be better to have a dedicated service with individual methods for specific clearing scenarios. This bug is about adding basic infrastructure for that using latest patterns for services like this.

Back to Bug 1757372 Comment 0