Open Bug 1310761 (groupedshistory) Opened 8 years ago Updated 2 years ago

[meta] Implement grouped session history across multiple <xul:browser> or <xul:remote-browser> elements

Categories

(Core :: DOM: Navigation, defect, P3)

defect

Tracking

()

People

(Reporter: freesamael, Unassigned)

References

(Depends on 5 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

I feel tasks related to this topic are enough to create a meta bug, so let's do it.
Depends on: 1276553
Depends on: 1276552
Depends on: 1310768
Depends on: 1310769
Depends on: 1310770
Depends on: 1310771
Alias: groupedshistory
Summary: Implement grouped session history across multiple <xul:browser> or <xul:remote-browser> elements → [meta] Implement grouped session history across multiple <xul:browser> or <xul:remote-browser> elements
Depends on: 1310766
Depends on: 1320735
Depends on: 1321688
Depends on: 1323650
Depends on: 1323651
See Also: → 1338479
Is the intention to enable this on Android as well? I'm asking because I've seen some desktop session store changes related to this and I haven't seen any equivalent changes being made on Android as well.

Bug 1340828 will probably help there, but I guess some further changes are needed for this to properly work...
Flags: needinfo?(sawang)
Depends on: 1340874
(In reply to Jan Henning [:JanH] from comment #2)
> Is the intention to enable this on Android as well? 

It was mainly for out-of-process prerendering use case so we didn't have any plan for Fennec as it's not e10s yet. In addition we're not actively working on prerendering stuff recently after blink announced their intention to unship prerendering and claimed prerendering benefits very few navigations [1].

GroupedSHistory could potentially benefit some other cross process navigation use cases in e10s or e10s-multi, but at this moment we don't have clear plan on adopting GroupedSHistory in other use cases either.

[1] https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/0nSxuuv9bBw
Flags: needinfo?(sawang)
After looking a bit further through this subject, I suspected that this might be only relevant with multiple processes, so thanks for the confirmation. That means I don't have to worry about it for the time being...
Marking all [meta] bugs as P3.
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.