Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v8bindings: Enable the fix of cross origin window name visibility #27956

Merged
merged 1 commit into from Mar 11, 2021

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Mar 9, 2021

Enables the fix of cross origin window name visibility in
production.

This fix was once applied back in 2017, but got reverted due to
a bug in youtube.com (not because the fix was wrong). We've been
disabling the fix since then. The bug in youtube.com was fixed
many years ago, so nothing should prevent us to enable the fix now.

https://chromestatus.com/metrics/feature/timeline/popularity/1872
shows the affected cases of this fix as 0.045% of page loads.
So, we shouldn't hit the same severe trouble like the one of
youtube.com in the past.

Bug: 538562
Change-Id: Ia28090493c2eb1f67d65de52f64690bb755ed38a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2734200
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#861825}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

Enables the fix of cross origin window name visibility in
production.

This fix was once applied back in 2017, but got reverted due to
a bug in youtube.com (not because the fix was wrong).  We've been
disabling the fix since then.  The bug in youtube.com was fixed
many years ago, so nothing should prevent us to enable the fix now.

https://chromestatus.com/metrics/feature/timeline/popularity/1872
shows the affected cases of this fix as 0.045% of page loads.
So, we shouldn't hit the same severe trouble like the one of
youtube.com in the past.

Bug: 538562
Change-Id: Ia28090493c2eb1f67d65de52f64690bb755ed38a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2734200
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#861825}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants