Amazon Kindle Block: block triggering several network requests

[liviopv]

Description

The Amazon Kindle embed block is continuiously triggering network requests when inserted in the editor, even when using the correct URL syntax (http://www.amazon.com/dp/ASIN, even though it accepts just any Amazon Kindle link). In some cases, this seems to be causing performance issues inside the editor, and also affecting the ability to switch templates.continuously.

Step-by-step reproduction instructions

1. Add an Amazon Kindle Block to a post or page
2. Add an Amazon Kindle link
3. Open the browser inspector in the Network tab

Screenshots, screen recording, code snippet

Environment info

• GB 17.6 RC 1, but the issue can be reproduced in 17.5
• Chrome 120
• Mac OS Sonoma

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[github-actions]

Hi,
This issue has gone 30 days without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest versions, you can help the project by responding to confirm the problem and by providing any updated reproduction steps.
Thanks for helping out.

[swissspidy]

This is probably an issue on the provider's end.

[kartikmehta8]

I tried reproducing the issue and yes, there are 100+ network calls made even for Reddit post embed as well.

I tried to create a function that will throttle the requests and tried it but the problem is that there are different URLs on which requests are being made.

/**
 * Throttling utility to limit request frequency.
 *
 * @param {Function} func The function to throttle.
 * @param {number} delay The delay in milliseconds between calls.
 * @return {Function} The throttled function.
 */
export const throttle = (func, delay) => {
	let timeoutId = null;
	return (...args) => {
		if (!timeoutId) {
			timeoutId = setTimeout(() => {
				func(...args);
				timeoutId = null;
			}, delay);
		}
	};
};

[Mamaduka]

This is a provider issue, and it's not actionable on the WordPress side.

A project can optimize embedded content rendering in various ways, but most are specific to providers. A popular example is the lite YouTube embed: https://github.com/paulirish/lite-youtube-embed.

I'm going to close this as "can't fix".