Currently, from the WebDriver or WebDriver BiDi client's perspective, the prerendered traversable is not distinguishable from the traversable created by user. This can cause an observable difference in test behavior with prerendering on and off.

Scenario

• User communicates to the browser via automation protocol (let's say WebDriver BiDi).
• User creates traversable_1.
• User navigates traversable_1 to a page_1 with a link to a page_2 and speculation rules for prerendering the page_2.
• (if prerendering is enabled) New traversable traversable_2 is created and navigated to page_2.
• User clicks on link.
• (if prerendering is enabled) traversable_1 is destroyed, traversable_2 is activated.
• (if prerendering is disabled) traversable_1 is navigating to page_2.

Currently, there is no way for automation clients to detect the switch of the traversable when prerendering is enabled. This will lead to unexpected test results, when user navigates to a prerendered page and assumes the traversable has not changed.