Context Navigation

Changes between Initial Version and Version 1 of Ticket #38367, comment 5

initial	v1
3	3	Users can normally embed videos using an embed code we provide them that involves using an iframe, which works as I expect when used directly in the WordPress editor. The oEmbed endpoint just returns that same embed code to be used in the HTML, so I'm not sure why I would be seeing different results here.
4	4
5		I did find [https://make.wordpress.org/core/2015/10/28/new-embeds-feature-in-wordpress-4-4/ this post] about embedding of other WordPress posts explaining some about sandboxed iframes. One thing I noted was that the ~~src attribute for the iframe~~ ends in /embed/ when embedding other WordPress posts. Screencast's content links also ends in /embed/ in the src to our embeddable iframe.
	5	I did find [https://make.wordpress.org/core/2015/10/28/new-embeds-feature-in-wordpress-4-4/ this post] about embedding of other WordPress posts explaining some about sandboxed iframes. One thing I noted was that the link ends in /embed/ when embedding other WordPress posts. Screencast's content links also ends in /embed/ in the src to our embeddable iframe.
6	6
7	7	This might be a long shot, but could the fact that our links end in /embed/ are resulting in WordPress embedding our content in this way without us being an oEmbed provider? Is there anything we can do about the iframe sandboxing so videos will work in the same way that using the embed code does?