Notes - Portal is safe to use and doesn't collect any user data. - Portal overrides some network requests to embed a live website in a safer way using declarativeNetRequest. - Portal ensures the network requests are overridden only in the new tab(empty url page) and doesn't effect your other web pages. - Although Portal overrides network requests, some websites use javascript to detect if it's embedded. Portal may not work well with those websites.

Performance Network aspect: Portal loads a webpage only when it's in viewport. So even if you have like 100 webpages embedded, the network request will be sent only when the webpage enters the viewport. Memory aspect: Currently, Portal doesn't flush out the webpage when it's out of viewport as it may need to be refetched again when in viewport. But I may give that as a option in future version to chose whether the user prefer memory or network performance.

This sounds really interesting, @sudoaugustin! I love the idea of turning the new tab into a more interactive space. But I'm curious, how does Portal handle those websites that use JavaScript detection? Are there any plans for added compatibility in future updates? Also, how does the sizing work for different screen resolutions? Would love to see more about the design aspects! 🛠️