New lifecycle callback for Turbolinks

javan · January 12, 2019, 7:09pm

See: https://discuss.hotwired.dev/t/controller-initialized-twice-when-visiting-from-a-turbolinks-page/17/3:

Controller initialized twice when visiting from a Turbolinks page

I believe everything is working as expected here. You’re seeing Turbolinks’ preview cache in action:

[D]uring standard navigation (via Application Visits), Turbolinks will immediately restore the page from cache and display it as a preview while simultaneously loading a fresh copy from the network. This gives the illusion of instantaneous page loads for frequently accessed locations.

The first controller is initialized when Turbolinks renders the preview. Then the preview <body> is replaced by fresh page content loaded over HTTP, which initializes a second controller.

Try these two things to confirm:

Log in connect() and disconnect() instead of initialize() . You should see a corresponding call to disconnect() for the first controller before the second controller connects.

Log the value of document.documentElement.hasAttribute("data-turbolinks-preview") . You should see true when Turbolinks is showing the preview.

Topic		Replies	Views
Controller initialized twice when visiting from a Turbolinks page	5	8008	February 17, 2022
Controller initialized twice	3	2179	May 22, 2018
Question regarding memory (w/ Stimulus + Turbolinks)	1	948	June 3, 2018
Turbo:render fired twice (not a cached preview) when following redirect_to triggered by Turbo link with frame '_top'	0	340	April 11, 2022
Turbolinks and POST requests	4	3669	May 5, 2020

New lifecycle callback for Turbolinks

Related Topics