Processed Issues22

This page shows a list of issues for svetandroida.cz that were approved or declined by our admins.

Template #1 Issue #1
Feb 4, 2019
According to Checklist:
3.3. Supported elements All important media (images, videos, slideshows, and other content that is relevant to the article) that exists in the source must be shown horizontally centered on IV page.

Here the image (with SIM-cards) at the article wasn't shown.
Accepted by admin
Template #3 Issue #1
Feb 6, 2019
Text is missing
Accepted by admin
Template #10 Issue #1
Feb 9, 2019
Related articles are missing, but they should be represented. These articles are about privacy / security / GPS / etc, which makes them thematically related to the main article. These articles are not "week-topics" since some of them were written several months ago.
See the Checklist, paragraph 6.3.2 "Related articles" ("It is obligatory to format “Related articles” links using the new <related> tag, provided they are identifiable in the source.").
Accepted by admin
Template #13 Issue #1
Feb 9, 2019
Those videos doesn't work on your template. I think IV doesn't fully support YouTube IFrame Player API. It's not YouTube bug, here is simple example of working iframe with the first "Sleep as Android" video: https://codepen.io/anon/pen/jdZvgX, which doesn't work in IV.
So, IV doesn't fully support this videos. According to the Checklist, paragraph 3.3: "Check that pages that feature unsupported content do not generate IV pages.". That's why this page shouldn't generate IV.
Den S.
You are right. If there are more than two videos a page, it stops working. I fixed it in Template #14.
Accepted by admin
Template #14 Issue #1
Feb 9, 2019
Page doesn't render
Den S.
IV shouldn't be generated for pages that require interaction. In this case it may not be as obvious as in polls articles [1], but should still be considered essential, because there is a whole lot of articles [2] like this one and all of them include comptetitions, which take 1/3 of an article.

[1] - https://www.svetandroida.cz/zakaz-pouzivani-mobilu-ve-skolach-hlasovacka/
[2] - https://www.svetandroida.cz/tag/tipy-z-ciny/
Declined by admin
The page requires interaction indeed. The contest is part of the article. It's better to generate no IV in this case.
Template #14 Issue #2
Feb 12, 2019
I am not sure about it, but I think these "catalog_rating" should be removed. On the initial page they are a part of the image, but on IV page they make no sense. I hardly believe that user would understand what these floating-point numbers stand for. Moreover they might be dynamic - if a user adds a review on an object its rating may change.
Accepted by admin
Template #14 Issue #3
Feb 12, 2019
In the original window a brief description of product is displayed as 1 list, not 2. Again, not sure how important that is.
Declined by admin
Template #14 Issue #4
Feb 12, 2019
Missed related news headline
Declined by admin
Template #14 Issue #5
Feb 12, 2019
App name is not a headline
Declined by admin
Template #14 Issue #6
Feb 12, 2019
I'm not sure but looks like anchors are missed
Accepted by admin
Anchor links must be preserved: https://instantview.telegram.org/checklist#3-3-supported-elements. The reporter's template properly handles them.
Template #20 Issue #2
Feb 12, 2019
Looks like anchors are missed
Accepted by admin
Anchors are missing. The reporter's template handles them.
Template #21 Issue #2
Feb 12, 2019
Looks like anchors are missed
Accepted by admin
Anchors are missing. The reporter's template handles them.
Template #26 Issue #1
Feb 13, 2019
The image is too small and it is technically possible to obtain the higher resolution version of it. It is fixed in my template. See 6.2.1 from Checklist:

6.2.1 Image quality
When several image resolutions are available, the IV page should use better quality images (within reason). The optimal resolution range is 1280px-2560px, using larger images is pointless. Note that images that are too large (>5 MB) will fail to load.

If for some reason it is only technically possible to obtain low-resolution versions of images (lower than 320px) for a page, on which high-resolution images are available on the web, the page should not generate an IV.
Accepted by admin
Template #30 Issue #1
Feb 14, 2019
Links to related articles are partly missing, but they should be represented. These articles are about privacy / security, which makes them thematically related to the main article. These articles are also identifiable (see template #31). Furthermore they are static enough - if you update the page, they won't change. So these articles are definitely related articles. According to Checklist, paragraph 6.3.2, they must me represented in IV: "It is obligatory to format “Related articles” <...>".
Even if you perceive these articles as not related, links to them must be in IV since they are not ad or something like this; see checklist, paragraph 3.3: "Anchor links must work properly on IV page if anchor links exist in the source."
Den S.
So these links, which you say I am missing, are in noscript tags. User doesn't see those links on the original page, the only scenario is scripts turned off. In fact IV shows noscript contents, but not these links. What it also shows is dublicates of cover images, which are also in noscript, but you don't seem to show them. Therefore, I consider showing the links this isssue is about optional or maybe even rudimentary - they are absent in original.
Declined by admin
Template #30 Issue #2
Feb 14, 2019
Answer to https://instantview.telegram.org/contest/svetandroida.cz/template30/issue1
I've checked the source code and didn't find any <noscript> tag inside / outside them. I have these links in the <article class="post-link"> tag.
What do you mean by "In fact IV shows noscript contents, but not these links."? As I said, I haven't any <noscript> tags in / out of them and I see those links in the "original" & "preview" windows.
Yes, IV shows images from <noscript> tag and I avoid duplicating images only because source page doesn't duplicate any (even if you turn off JS), not because they are in the noscript tag.
If a user can see them on the page without accessing html code, they are not absent.
Den S.
Weird, it doesn't show for me sometimes. You are right, it is better to include the links. Fixed in new template (all related articles articles are at the end).
Accepted by admin
Template #32 Issue #1
Feb 15, 2019
Missing related articles
Den S.
They are present below, in related block. I just moved them.
Declined by admin
Template #32 Issue #2
Feb 15, 2019
This is not a headline
Den S.
There are no rules for that. All content is present, image size preserved, buttons changed to links. Note that all articles containing an appbox are about those apps and the original style gets user attention thanks to that big blue button. So I chose header to compensate that, plus it is a perfect way to make it look like a block, like in original.
Declined by admin
Template #32 Issue #3
Feb 15, 2019
Original images have links to other pages.
Den S.
Right. Fixed in Template #35.
Accepted by admin
Template #35 Issue #1
Feb 18, 2019
No Instant View available
Den S.
Right. Fixed in #44.
Accepted by admin
Template #40 Issue #1
Feb 20, 2019
Trivial nested element issue. No usnupported elements, should be generated.
Accepted by admin
Denis template supports everything.
Template #48 Issue #2
Feb 22, 2019
Header is missed, text is not indentet properly. Also, this is an aside, not a blockquote.
Accepted by admin
Idris Yandarov
it's not a pull quote, these blocks are styled differently, but they have no quotations, check what pull quote is here: https://en.wikipedia.org/wiki/Pull_quote
or here: https://www.smashingmagazine.com/2008/06/block-quotes-and-pull-quotes-examples-and-good-practices/
check also classes of this boxes, they are simple "notes", not "quotes"
however it's not a block quote too.
Accepted by admin
The div class="box-note" shouldn't be formatted properly, but pullquote and blockquote are not suitable for it
Template #49 Issue #1
Feb 23, 2019
Pull quotes are short excerpts from the presented text. They are used to pull a text passage out of the reader’s flow and give it a more dominant position in the post or the article. The pulled out passage should be mentioned somewhere in the text as this pulled out passage refers to the current text, it's a kind of internal quote. Here highlighted blocks are independent blocks of text, not a quotations at all. Therefore it's inappropriate to use <aside> for ".box-note" blocks here.
Here is pretty simillar case: https://instantview.telegram.org/contest/informer.rs/template33/issue2/
Den S.
The answer:
https://telegra.ph/On-Issue-2-02-23
Accepted by admin
The block should be visually separated from the main text. But it's not a pullquote. The Template #51 handles this page better