On Fri, Sep 11, 2020 at 10:55 PM Shuran Huang wrote:
> Thanks for the pointer. I did not realize it's about the cross-origin
> navigation that not switch BrowsingInstance. Just to confirm, is the case for
> top-level navigation only or not?
Cross-origin navigations of top-level browsing
On Friday, September 11, 2020 at 11:26:59 AM UTC-4, Anne van Kesteren wrote:
> On Fri, Sep 11, 2020 at 5:00 PM Shuran Huang wrote:
> > FYI, here is the tracking bug for this issue in Chrome: crbug.com/1090128.
>
> Hey Shuran,
>
> I think the bug you're looking for is
>
On Fri, Sep 11, 2020 at 5:00 PM Shuran Huang wrote:
> FYI, here is the tracking bug for this issue in Chrome: crbug.com/1090128.
Hey Shuran,
I think the bug you're looking for is
https://bugs.chromium.org/p/chromium/issues/detail?id=706350. In
particular this intent to ship is about resetting
On Thursday, September 10, 2020 at 8:47:37 AM UTC-4, Tim Huang wrote:
> Summary:
>
> The window.name can persist after doing cross-origin navigation, which
> means it can leak information across origins and be used as a tracking
> vector.
>
> To address this, we want to clear the window.name
Summary:
The window.name can persist after doing cross-origin navigation, which
means it can leak information across origins and be used as a tracking
vector.
To address this, we want to clear the window.name when doing cross-origin
navigations. The window.name won't persist across origins, so
5 matches
Mail list logo
