probably because people will generally search the element again on the new page, which will overwrite the outdated ref with an uptodate one.

The issue would only be triggered if you have some XPath coming from another source than a ``find()`` call on the current page. This can be an element instance from a previous page, or a direct usage of the driver.