Skip to content

newsletter: Add a section about Google reCAPTCHA #169

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 28, 2025
Merged

newsletter: Add a section about Google reCAPTCHA #169

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added public/assets/img/newsletter-july-2025-google-recaptcha.mp4
View file
Open in desktop
Binary file not shown.
15 changes: 15 additions & 0 deletions src/content/newsletters/2025-07-31.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,21 @@ will now render up to 120 times per second on a 120Hz screen. This also affects

![](/assets/img/newsletter-july-2025-high-refresh-rate.png)

### Google reCAPTCHA passing

There was a long standing issue with our [postMessage](https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage) implementation
where if the serialized type was not used in the destination realm before, we would fail to reconstruct it because it did not think it was
available in that realm.

This was fixed this month, allowing Google reCAPTCHA to work and pass!

<video controls style="margin-bottom: 2em">
<source src="/assets/img/newsletter-july-2025-google-recaptcha.mp4"></source>
</video>

Unfortunately, it does not work on origins that are not https://www.google.com/ due to a separate same-origin policy issue that has not been
resolved.

### Credits

We'd like to thank everyone who contributed code this month:
Expand Down