[wp-trac] [WordPress Trac] #61941: Adding app.screencast.com as an oEmbed provider

[WordPress Trac]

#61941: Adding app.screencast.com as an oEmbed provider
-------------------------+-----------------------------
 Reporter:  brhodes      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+-----------------------------

Comment (by swissspidy):

 Thanks for the ping. As per my previous comment, it's important that a
 provider and the oEmbed API is well-established and well-documented. Right
 now my impression is that the endpoint is still in its infancy and not yet
 mature. The fact that the endpoint didn't adhere to the discovery spec
 until it was pointed out here confirms that.

 So regarding that point, my main guidance right now is to just wait and
 see this become more established and robust. We can then revisit this next
 year or so.

 Note: That's also why I recommended moving the documentation from
 https://docs.google.com/document/d
 /1NzamkRo1NKYc6leCuu1wvAolQAU2L4hItzPN60e-BzU/edit to a public website.

 Ideally another core contributor here chimes in as well so we can hear
 their thoughts. (cc @azaozz @peterwilsoncc)

 ----

 The good news is with your latest fixes the oEmbed discovery now works for
 your content as expected! i.e. you can drop a Screencast URL in the editor
 and it gets embedded.

 The downside is that the embed won't load. That's because the iframe is
 sandboxed (since the provider isn't allowlisted yet), and you are loading
 some JavaScript that tries to access `document.cookie`. That doesn't work
 because of the sandboxing and results in a `SecurityError`

 Then there are also some console warnings about the page using
 `document.write`.

 You can reproduce this using the following snippet that's generated by
 WordPress:


 {{{
 <iframe class="wp-embedded-content" sandbox="allow-scripts"
 security="restricted" title="oEmbed link type encoding" scrolling='no'
 frameborder='0' width='500' height='75'
 src='https://app.screencast.com/connector/embed/index/YAdPyx6PygL6N#?secret=66UvUE2BUq'
 data-secret='66UvUE2BUq'></iframe>
 }}}

 If your content can at least be ''displayed'' in such a sandboxed iframe,
 that makes it easier for everyone on the web to leverage your oEmbed
 endpoint and help make it more established and stable.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61941#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform