As a prerequisite to return navigation ids in various commands and events, we should create a helper/utility that will be able to track navigation for all contexts, and return the current navigation id for any context. Tracking the navigations might be handled in the parent or content processes, however the service itself should be available in the parent process: - need to access the unique context ids - network events (which need a navigation id when relevant) are handled in the parent process
Bug 1841010 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.
As a prerequisite to return navigation ids in various commands and events, we should create a helper/utility that will be able to track navigation for all contexts, and return the current navigation id for any context. Tracking the navigations might be handled in the parent or content processes, however the service itself should be available in the parent process: - need to access the unique context ids which are only available in the parent for now - network events (which need a navigation id when relevant) are handled in the parent process