Page Lifecycle
After I change a booking and return to the list, why is the old time still there?
Pottery workshop
Triggered page callbacks
list.onLoad list.onShow list.onReady
Creating the list instance triggers onLoad and onReady once in this example.
Initialize once for this instance: onLoad handles initial parameters; onReady indicates the initial view is ready. Neither callback means a data request has completed.
Respond when the page reappears: onShow can run multiple times on the same instance. Refresh data that may have changed; onHide can pause work and onUnload can clean up resources.
Send this to the AI Agent in your project
After editing booking details, the list still shows the old time on return. Check the page lifecycle: is data loaded only in onLoad, and should onShow refresh it? Repeat entering details, editing, and returning twice; verify the latest booking appears without duplicate requests.
Select page elements for precise AI edits
Click a button, text, or card, note the change, then copy its exact location to AI.
Open Selector Pro website↗