Closed Bug 1161665 Opened 9 years ago Closed 8 years ago

Don't create a history entry for a prerendered document that user never navigates to

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1310761

People

(Reporter: tanvi, Unassigned)

References

(Blocks 1 open bug)

Details

If a prerendered link is never clicked on by the user, remove the history entry after the prerendered docshell is destroyed.  (Or don't create one in the first place, whatever is easier implementation wise.)
I believe this is covered by groupedshistory.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
(In reply to Samael Wang [:freesamael][:sawang] from comment #1)
> I believe this is covered by groupedshistory.
> 
> *** This bug has been marked as a duplicate of bug 1310761 ***

How is 1310761 a dupe of this bug?  How will this bug get addressed with the meta bug?
(In reply to Tanvi Vyas - behind on bugzilla [:tanvi] from comment #2)
> (In reply to Samael Wang [:freesamael][:sawang] from comment #1)
> > I believe this is covered by groupedshistory.
> > 
> > *** This bug has been marked as a duplicate of bug 1310761 ***
> 
> How is 1310761 a dupe of this bug?  How will this bug get addressed with the
> meta bug?

Oh. We're taking an approach more like "don't create one in the first place" you mentioned in comment 0. 

A prerendered page will be in a background hidden tab, which has its own session history object and can potentially be in another process.

That's why we're implementing GroupedSHistory for prerendering. On adopting a prerendered tab, we'll create a grouped session history across original tab and the prerendered tab, which allow us to keep bfcache work even if prerendering was out of process. And by doing so, conceptually the session history entry is added only when the prerendered tab is adopted. If it's never adopted we simply close the hidden tab.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.