Preview
Issue #3
this template adding extra linebreaks for some strong tags. it occurs for another pages too.
- Deleted Account
- Blanks spaces are not critical
- Accepted by admin
- This is a critical issue. Splitting the text in this way ends up with an IV that is much less readable. It looks like a corrupted IV.
It would be better if a reader views the original page in a browser than to show the user a corrupted IV.
- Deleted Account
- I have a question regarding another template.
Why did you rejected my issue https://instantview.telegram.org/contest/news.day.az/template21/issue1/?
According to your checklist: "If it is not possible to represent the widget as an iFrame, but it is possible to get a direct link to the video, use this link to generate a <video> with the correct src attribute." - https://instantview.telegram.org/checklist#6-8-2-videos-from-unsupported-players
In other words, the template does not meet your "Perfect Template Checklist" criterias. Yet the issue pointing this was rejected by an admin. Why?
P.S. Note that in all previous cases the templates that didn't meet this criteria were rejected, for example: https://instantview.telegram.org/contest/milliyet.com.tr/template1/issue1/
So, what makes the issue https://instantview.telegram.org/contest/news.day.az/template21/issue1/ different from others?
- Accepted by admin
- As the decline comment says: "Template #21 represented video as an iFrame." That is why the error shown there is, "EMBED_NOT_SUPPORTED".
The iframe method is generally better than the <video> tag method. Even if the iframe widget is not currently supported by Telegram, once Telegram supports the widget, the template will be able to instantly generate an IV with working video without requiring modification of the template code.
In contrast, using <video> tags has greater limitations than the iframe method, such as video src URLs being potentially dynamic and limitations on the filesize of such videos used.
As for the other issue you mention, it uses neither the iframe method nor the <video> tag method. Such a template will not be able to support video unless the template itself is modified to include video support in the future.
- Type of issue
- Author added their own content
- Reported
- Jun 19, 2017