[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 brhodes):

 I do want to clarify that https://app.screencast.com isn't a new provider,
 but a rewrite and migration of www.screencast.com. We expect by the end of
 this year all the existing users of www.screencast.com will be migrated
 over to https://app.screencast.com and the old site will be shut down next
 year.

 We have existing customers of Classic Screencast unhappy that now they are
 migrated to the new Screencast their media no longer works in WordPress.

 We did have some issues with how we implemented oEmbed in
 app.screencast.com, but depending on the tool we used to test oEmbed these
 tools unfurled the media even with the errors you pointed out. But I'm
 glad we are in a better spot with oEmbed support.

 To your point about sandboxing, if I understand you correctly when
 https://app.screencast.com is on the allowlist the iframe will contain:

 {{{
 sandbox="allow-scripts allow-same-origin allow-presentation"
 }}}

 "allow-same-origin" is required for our view page to work and testing out
 our Screencast Classic embeds that value is added to the sandbox attribute
 for those media.

 We do not plan on getting our media iframe embeds working without "allow-
 same-origin".

 The last point about public api documentation, this is something I believe
 we can make happen.

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