Disable Optimization Detective by default on the embed template #1472
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was doing some testing with post embeds and I tried embedding a post embed from my blog onto my local test environment. When I did so, I saw an error in the console:
Normally the embed template doesn't have any external scripts, but since Optimization Detective is running on my site it is adding a script module to the page that does a dynamic import of
detect.js
. This then is causing an error because the WordPress post iframe is served withsandbox="allow-scripts"
which doesn't includeallow-same-origin
, meaning the Same-Origin Policy is being enforced, blocking the loading of the script (as I understand).The solution is simply to disable Optimization Detective for the embed template. In reality there is not really a need for optimizations to run on the basic embed template, as there is at most only one or two images and everything is in the viewport. WordPress core is already adding
fetchpriority=high
to the featured image in a post embed template.