The problem arises because the automation framework is unable to detect the transition to the new page, resulting in subsequent methods failing due to the automation still referencing elements from the previous page, as the document context has not updated to the new tab. This issue typically occurs when the automation tool fails to synchronize with the browser's tab switching mechanism, causing a disconnect between the expected page state and the actual page state within the automation workflow.
And there's no mechanism to get the current_tab. So I added a fix here self._tabs[activated_tab_id] this can used as an alternative method but it's still more competent if we have a built-in method for getting the current_tab
The problem arises because the automation framework is unable to detect the transition to the new page, resulting in subsequent methods failing due to the automation still referencing elements from the previous page, as the document context has not updated to the new tab. This issue typically occurs when the automation tool fails to synchronize with the browser's tab switching mechanism, causing a disconnect between the expected page state and the actual page state within the automation workflow.
And there's no mechanism to get the current_tab. So I added a fix here
self._tabs[activated_tab_id]this can used as an alternative method but it's still more competent if we have a built-in method for getting the current_tab