When providing a url to the service, some magic (oEmbed call) is used to transform that url into a player snippet for the corresponding service.
When reading the returned markup: there is no way to know the source url.
Assuming our current ESI include issues will be fixed, this will be the next problem for importing the content from the HTML markup. To solve and assuming we'll get rid of this service after the Blog content will be "re-imported" and transformed into a block based content (vs "inline" and sections at the moment), I propose to add the source url as a data attribute of the parent div in the embed snippet.
Like this, it is easy to find via a dom query and transform into the appropriate table.
When providing a url to the service, some magic (oEmbed call) is used to transform that url into a player snippet for the corresponding service. When reading the returned markup: there is no way to know the source url.
Assuming our current ESI include issues will be fixed, this will be the next problem for importing the content from the HTML markup. To solve and assuming we'll get rid of this service after the Blog content will be "re-imported" and transformed into a block based content (vs "inline" and sections at the moment), I propose to add the source url as a data attribute of the parent div in the embed snippet. Like this, it is easy to find via a dom query and transform into the appropriate table.
@MarquiseRosier @tripodsan @trieloff WDYT ?