Google says {that a} code snippet with Zero Attribution was a bug, not a check

Google mentioned that the code fragment submitted with out attribution was a bug and that 100% of what Google is at the moment testing. Google's Danny Sullivan was very sad about having certified this check check after I by no means requested Google in the event that they have been truly testing it. He’s proper. Truthfully, I by no means thought that individuals would assume that Google had mentioned that it was a check. So I make it clear by writing a brand new message that it was truly a bug and never a check.

Briefly, it was a Google bug, however I didn’t say that it was one thing Google was testing whereas Google was not testing it – it was only a bug.

Here’s a screenshot of the bug the place Google confirmed a particular textual content snippet, however this one was not attributed to Wikipedia, the supply of the featured snippet:

Once more, Google didn’t intend to do it, it was a bug. Though the absence of favicons on this screenshot is a function that, in keeping with Google, is a function – extra about it right here.

Danny Sullivan mentioned on Twitter "Sure, I can verify that there’s a bug – not a check – occurring in Firefox for Android, we’re engaged on debugging it now. "

He then defined how my article had been revealed, claiming that Google had confirmed that it was a bug. Let's be clear: at no level within the writing of this text did I even assume that I implied or prompt that Google verify this as a check.

No matter it’s, Google had a bug, my story about it might have been found by the truth that Google confirmed that they have been testing this as a function. I didn’t need that to occur. I simply noticed a screenshot of this film in motion, I lined it and a few folks have been misinterpreted. I’m sorry for any confusion.

Dialogue Discussion board at Twitter.