Navigates the original tab to some unwanted content (usually ads)
We tried to implement a solution in Chrome where we would detect the final navigation at (2) and block it with some UI. See design doc here
The current classification of tab-unders is in the code here:
// Currently, navigations are considered tab-unders if:
// 1. It is a navigation that is "suspicious"
// a. It has no user gesture.
// b. It is renderer-initiated.
// c. It is cross site to the last committed URL in the tab.
// d. The navigation started in the background.
// 2. The tab has opened a popup and hasn't received a user gesture since then.
However, there are some legitimate use cases for tab-unders as currently defined. For instance, a site that opens popups (like a email site) might want to automatically redirect to a third party auth provider in the background when a session ends.
We'd appreciate any bright ideas from the community about how to best address these issues.
A tab-under is when a tab:
We tried to implement a solution in Chrome where we would detect the final navigation at (2) and block it with some UI. See design doc here
The current classification of tab-unders is in the code here: // Currently, navigations are considered tab-unders if: // 1. It is a navigation that is "suspicious" // a. It has no user gesture. // b. It is renderer-initiated. // c. It is cross site to the last committed URL in the tab. // d. The navigation started in the background. // 2. The tab has opened a popup and hasn't received a user gesture since then.
However, there are some legitimate use cases for tab-unders as currently defined. For instance, a site that opens popups (like a email site) might want to automatically redirect to a third party auth provider in the background when a session ends.
We'd appreciate any bright ideas from the community about how to best address these issues.
cc @ojanvafai @jkarlin