- Sardar Atabekov
- As you wrote: "the widget is already represented as iframe".
"If the unsupported widget has an iFrame version, make it into an <iframe>. If you do that, the IV page will not be generated due to unsupported content, but things will work out of the box if and when we support that widget."
Then, if there is no possibility iframe version
"If it is not possible to represent the widget as an iFrame, but it is possible to get a direct link to the video/audio, use this link to generate a <video> or <audio> with the correct src attribute. "
Why report the last minute about this. You first see your template, which has a lot of problems than mine (8issue)
In addition, your template still does not support video on all pages that contain video
- Declined by admin
- Type of issue
- IV not generated for target page
- Mar 30, 2019
"If it is not possible to represent the widget as an iFrame, but it is possible to get a direct link to the video/audio, use this link to generate a <video> or <audio> with the correct src attribute."
Although the widget is already represented as iframe, it is very unlikely that it will be supported officially by Telegram, since it is not on one of popular platforms. However, video source can be extracted using @inline, and it is better to do so. In my template, I extract the correct src attribute and insert the <video> tag in the place of the iframe, and I believe that mine is the correct approach