This apparently comes from the “embed” used in the url.
There seems to be no short-term solution at the moment
